Your lightweight open-source personal agent.
Python agent-frameworkai-agentai-agentschatbotchatopsdiscord-botllm-agentsllmslocal-llmmcpmodel-context-protocolmulti-agentopenai-compatibleopenclawpersonal-ai-assistantpythonself-hostedtelegram-bot-ai-assistantwebuiworkflow-automation
Working on nanobot
The Python gateway owns agent execution, sessions, tools, memory, and security policy. WebUI and TUI share that runtime; keep execution and policy out of the clients.
Task-specific guidance
| When working on | Read |
|---|---|
| Finding the owning code and focused tests | .agent/navigation.md |
| Core boundaries, extensions, or internal types | .agent/design.md |
| Refactoring, fallbacks, or test selection | .agent/simplify.md |
| User-facing copy, feature naming, or localization | .agent/copywriting.md |
| Path permissions, HTTP/MCP, or shell isolation | .agent/security.md |
| Dependency setup, WebUI transport, config, Windows, prompts, or persistence | .agent/gotchas.md |
| Reusing verification evidence | .agent/workflow.md |
| WebUI/host compatibility | .agent/review-guide.md |
| Contribution or publication | CONTRIBUTING.md, docs/releasing.md |
Development constraints
- Analyze the required behavior, state ownership, and root cause before extending existing code. Refactor when the structure causes the problem; a smaller diff does not justify another fallback.
- Do not add defensive tests for hypothetical internal states or unsupported combinations. Each new test needs a reachable path and a meaningful contract to protect.
- Do not add tests merely to prove that nonexistent behavior, removed code, or obsolete symbols are absent. Negative assertions must exercise a concrete, reachable risk and protect an observable behavioral contract; prefer testing supported actions and their results.
- Do not run
ruff format; mechanical formatting obscures git blame and creates unrelated diffs. This constraint takes precedence over the optional touched-file formatting inCONTRIBUTING.md. - Do not manually wrap prose in Markdown files. Keep each paragraph on one source line; use line breaks only for Markdown structure.