.downcity Directory
Runtime data layout and what each folder is for
.downcity/ Directory
~/.downcity/ is Downcity's user-level configuration and runtime data directory. Downcity does not create a .downcity/ directory inside each project.
Typical layout
~/.downcity/
├── agents/<agent_id>/
│ ├── agent.json
│ ├── SOUL.md
│ └── workspaces/<workspace_id>/
│ ├── sessions/
│ ├── archived-sessions/
│ └── logs/
├── plugins/<plugin_id>/
│ └── config.toml
├── runtimes/city/
└── downcity.dbKey folders
agents/<agent_id>/workspaces/<workspace_id>/logs/
Daily JSONL logs: <YYYY-MM-DD>.jsonl.
agents/<agent_id>/workspaces/<workspace_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.
Plugin runtime data
Plugin-owned runtime data uses the private storage scope exposed by the current AgentWorkspace context. Plugin definitions and profiles remain under ~/.downcity/plugins/<plugin_id>/.
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 configuration, conversations, tokens, and execution traces.- Do not commit or copy the directory to an untrusted location.