What Makes Craft Agents Different
Familiar interface
The inbox works like a combination of email and task manager. Each conversation has a status, persists between sessions, and can be organized however you want. Review agent plans before execution in document-like interface, just like reviewing work from a colleague.Connect to anything
Sources give the agent access to your tools—MCP servers, REST APIs, or local files:| Source Type | Examples | What You Can Do |
|---|---|---|
| MCP servers | GitHub, Linear, Craft | Full integration with issue tracking, docs, repos |
| REST APIs | Any service with an API | Query and mutate data from internal tools |
| Local files | Obsidian vaults, code repos | Work with files on your machine |
Multitask naturally
Start multiple tasks. Jump between conversations with full history preserved. Run long tasks in the background while you work on something else.Explore, then execute
Start in Explore mode—read-only by default. Let the agent research, analyze, and draft a plan. Review proposals before any changes happen. Once aligned, switch to Execute and let it work autonomously.Sessions become documentation
Every conversation captures decisions, trade-offs, and implementation details. Share sessions with your team. Attach them to Linear issues, GitHub PRs, or Confluence pages so others understand not just what changed, but why.Fully customizable
Themes, skills, statuses, permissions—everything is a config file the agent can edit. Modify behavior through conversation, not complex settings UIs.| What | How It Works | Customization Level |
|---|---|---|
| Skills | YAML frontmatter + markdown | Reusable instructions invoked with @mention |
| Themes | 6-color semantic system | App or workspace, with dark mode and scenic backgrounds |
| Statuses | Config for workflow states | Custom labels, colors, icons, inbox/archive categories |
| Permissions | Layered rules | App → workspace → source cascade |
Craft Agents vs Claude Code
Craft Agents and Claude Code share the same foundation—the Claude Agent SDK—but serve different purposes:| Aspect | Claude Code | Craft Agents |
|---|---|---|
| Interface | Terminal CLI | Easy to use desktop app |
| Data sources | MCP servers | MCP + REST APIs + local files |
| Session org | Continue with -c flag | Inbox with custom workflow statuses |
| Config scope | Per-project .claude/ | Multi-workspace with full isolation |
| Permissions | Fixed mode behaviors | Customizable rules per workspace/source |
Key Concepts
Sources connect Craft Agents to external data—GitHub repos, Linear projects, Craft spaces, or your local filesystem. Each source gives the agent new capabilities. Workspaces are isolated environments with their own sources, skills, and sessions. Use different workspaces for different projects or contexts. Permission modes control what the agent can do. Cycle through them with SHIFT+TAB:| Mode | Behavior |
|---|---|
| Explore | Read-only. Research and analyze without risk. |
| Ask to Edit | Prompts before changes. Review each action. |
| Execute | Full autonomy. The agent works uninterrupted. |