Agents
Supaspec tracks AI agent contributions to your projects. Every write operation records which agent made the change.
Agent Self-Identification
Agents identify themselves using an agent_name parameter on every write operation. This is a simple snake_case string like claude_code or cursor.
Auto-Registration
When an agent first interacts with a project via a write operation, Supaspec automatically creates an agent record with:
- • A display name (e.g., “Claude Code”)
- • A UI color for visual distinction
- • Activity timestamps (first seen, last seen)
No manual setup needed.
Color-Coded Attribution
Each agent gets a unique color for badges, revision logs, and proposals:
| Name | Display | Color |
|---|---|---|
claude_code | Claude Code | |
cursor | Cursor | |
codex | Codex | |
windsurf | Windsurf | |
copilot | Copilot | |
(custom) | Custom Agent |
What Gets Tracked
Agent attribution is recorded for:
- •Section commits (who edited what)
- •Version history (agent badge on each version)
- •Proposals (who proposed changes)
- •Revisions (who updated a proposal)
- •Comments (who left feedback)
- •Accept/reject actions (who approved or denied changes)
Agent Dashboard
Each project has an Activity page showing all agents that have interacted with the project, along with per-agent statistics and a timeline of contributions.
Security Model
Agent identification is trust-based. Since you control your own tools and API keys, agent names serve attribution purposes, not security. An agent could technically claim to be a different agent, but since you're the one configuring the tools, this is a non-issue in practice.