AgentGraft
Documentation
AgentGraft puts an AI assistant inside your Django app. You describe its tools, agents and voice in one Python file, push it with one command, and show it with one template tag. Your code stays the source of truth; AgentGraft runs the conversation, the streaming and the memory.
Pages
- Get started
- Quickstart From an empty Django app to a working chat widget in seven steps and roughly five minutes. 5 min
- Concepts The seven words you need to navigate the rest of these docs without flinching. 4 min
- Reference
- The SDK Seven decorators, one settings dict, one CLI command. The full Python surface, in one page. 8 min
- Wire protocol Everything that crosses the network between your browser, AgentGraft, and your host app. 6 min
- Operations
- Embedding the widget Everything that breaks between dropping the template tag and seeing the chat bubble — CSP, CORS, async views, identity — with the exact rules for fixing each one. 8 min
- Deployment From a working local integration to one that auto-syncs on every push, without breaking the first deploy. 5 min
- Importing users and conversations Backfill end users, conversations, and messages from another platform in one POST so migrated visitors arrive with history intact and the Dreamer builds long-term memory from day one. 5 min
- Guides
- Building systems of agents How to design multi-agent grafts that actually work — tool contracts, parameter descriptions, handoff discipline, the orchestrator pattern, and per-agent model assignment. 7 min
For agents
The docs are also published in the llms.txt format, so an AI assistant can read all of it in one fetch. Plain text, no auth.
- llms.txt A short index: every page with its summary and URL. Index
- llms-full.txt Every page, concatenated into one plain-text file. Full text
fetch("https://agentgraft.com/docs/llms-full.txt")How it's built
Configuration lives in code
Every tool, agent and prompt is in one Python file in your repo. The dashboard is read-only, so nothing drifts away from the code.
Sync is all or nothing
One command pushes the whole file, and the server applies it in a single transaction. To roll back, revert the commit and sync again.
Identity stays in your app
AgentGraft never stores your users.
The widget signs an opaque id, and your @ag.user_loader turns it back into your own user inside your tools.