Repository Structure

Directory layout — what lives where, with subsystem README pointers

Details

work_buddy/ = Python package. Key top-level modules: agent_session.py (identity), artifacts.py (centralized store), paths.py (path resolution), tools.py (feature toggles), config.py (config.yaml + config.local.yaml overlay), consent.py (SQLite-backed), workflow.py (DAG engine).

Key packages: knowledge/ (agent docs: query, index, store, editor, vault adapter), dashboard/ (Flask + frontend/ package), health/ (diagnostics engine, checks, components), collectors/ (16 sources), mcp_server/ (gateway + activity_ledger.py), sessions/ (conversation inspector), notifications/ (surfaces: obsidian, telegram, dashboard), messaging/ (inter-agent), memory/ (Hindsight), telegram/ (bot), threads/ (chat system), projects/ (registry + Hindsight observations), triage/ (Chrome tab pipeline), llm/ (API wrappers), chrome_native_host/ (extension host), obsidian/ (bridge, vault_writer, tasks, tags, smart, datacore, ktr, day_planner, vault_events, commands), calendar/, journal_backlog/.

knowledge/store/ = workflow definitions + agent docs (JSON). contracts/ = live data. sidecar_jobs/ = scheduled job definitions.

data/ = all generated data (gitignored): agents/ (per-session: consent.db, manifests, logs, ledgers), context/ (bundles), runtime/ (PID, state, tool status), cache/ (LLM, chrome tabs), chrome/ (ledger), db/ (SQLite: messages, tasks, projects), logs/ (debug logs), commit/ (90d TTL), export/, report/, scratch/ (artifact types with TTL lifecycle).

.claude/commands/ = 34 slash commands (thin launchers loading from knowledge store).