.downcity/ Directory

.downcity/ is Downcity's local runtime data directory. In most projects, it should not be committed to Git.

When Downcity initializes a project, it automatically appends .downcity to that project's .gitignore.

Typical layout

.downcity/
  logs/
  agents/
  chat/
  task/
  data/
  public/
  resources/
  .cache/

Key folders

.downcity/logs/

Daily JSONL logs: <YYYY-MM-DD>.jsonl.

.downcity/agents/<agent_id>/sessions/<session_id>/messages/

Conversation source of truth: active.jsonl, assistant_message.json, and sequence-named segments/*.jsonl.

Agent Memory

Long-term Memory is not part of the Workspace .downcity/ contract. Memory content is owned by the Agent's active MemoryProvider. The built-in File Adapter defaults to ~/.downcity/agents/<agent_id>/memory/; other Providers can use databases or remote services.

.downcity/chat/

Chat metadata and history event streams. access.db stores this Agent's Chat principals, requests, allow/deny grants, and audit events. migration-backup/authorization/ contains legacy authorization JSON after one-time migration.

.downcity/channel/meta.json

Channel-target to session_id mapping snapshot (managed by chat plugin runtime).

.downcity/task/

Task definitions and per-run artifacts (run.json, result.md, etc.).

Skills location

SkillPlugin scans .agents/skills (project) by default. If use: ["home"] is enabled in the constructor, it also scans ~/.agents/skills (user).

Security guidance

• .downcity/ may contain sensitive conversations and execution traces.
• For debugging, prioritize logs, task, and agents.