Tech Stack Decisions
Overview
Technology choices for the One Mind system. Every tool must earn its place — if a plain markdown file can do the job, we don’t add a tool.
Current Stack
| Layer | Tool | Why |
|---|---|---|
| Knowledge | Obsidian | Local-first, plain markdown, git-syncable |
| Tasks | Todoist | Fast capture, natural language, API for agents |
| Agents | OpenClaw | Multi-agent gateway, extensible skills |
| Worker agents | Agno AgentOS | Python-native, team composition |
| Messaging | NATS JetStream | Fast pub/sub, durable streams, cross-runtime |
| Smart home | Home Assistant | Local control, massive device support |
| Database | PostgreSQL + pgvector | Relational + vector search for agent memory |
| Automation | n8n | Visual workflow builder, self-hosted |
| Voice | LiveKit | Real-time audio/video, low latency |
| Version control | Git + GitHub | The codex is a git repo — everything is versioned |
Guiding Principles
- Plain text first — The codex is markdown. No proprietary formats.
- Self-hosted preferred — Own the infrastructure when possible
- API access required — If agents can’t read/write it, it doesn’t make the stack
- Replaceable — Every tool should be swappable without losing data