Team developer
You build stories with an agent in a team, and review what it opens.
You build stories with a coding agent inside a team. Your agent needs to know what binds for the story in front of it — the requirement, its criteria, the constraints and decisions around it — and your teammates need to trust that what it builds matches what was agreed.
In Corpole your agent connects under your own name and acts with your permissions. It reads the story's work context before it touches code, names the codes it follows in the branch and the pull request, registers tests against the criteria, and leaves a handover note when it stops halfway. You write your own agent rules on top of the project's.
This page gathers what a developer needs: connecting, setting up the repository, picking up Ready work, the check on pull requests, and what to do when the agent goes off course.
Start here
- Connect your agent under your own identity: OAuth, or a personal agent token.
- Run /corpole:init in the repository so the agent puts Corpole above the files in the repo.
- Ask the agent to pick a Ready story; it reads the story's work context before coding.
- Name the story or record code in the branch and pull request, so the check and the traceability line up.
- Write your own rules for the agent, on top of the project's.
Getting started
Connect your agent
- GuideAgents
- How-toConnect Claude Code
- How-toConnect Cursor, VS Code and other MCP clients
- ConceptPersonal tokens, service tokens and sign-in
- How-toSet up your repository with /corpole:init
- ConceptHow the GitHub check works
- How-toNo MCP? Use the REST endpoint or a CLAUDE.md snippet
- ConceptRead-only or propose: what a connection may do
Records & authority
Relations & conflicts
Work & boards
Knowledge
Agent policy & rules
Traceability & quality
Existing codebases
When things go wrong
- CaseMy agent forgot what we decided yesterday
- CaseMy agent followed a decision we had dropped
- CaseMy agent changed a requirement to fit its code
- CaseThe requirement changed while the agent was working
- CaseThe agent says "done" but a criterion is not met
- CaseThe same test keeps failing
- CaseThe agent wants to run a migration or add a dependency
- CaseProduction is down: declaring an emergency
- CaseA secret ended up in something the agent wrote
- CaseA file or web page tells the agent to do something
- CaseTwo agents picked the same story
- CaseI just need to fix a typo
- CaseWe keep making the same mistake
- CaseA new developer joins mid-project
- CaseI inherited a half-built vibe-coded app
- CaseMy agent insists on something Authority forbids
Team & accounts
Security & data
Troubleshooting
- Troubleshooting401 invalid_token
- TroubleshootingClaude Code shows corpole as failed
- TroubleshootingThe agent's proposal was refused
- TroubleshootingMy agent ignores the requirements
- TroubleshootingMy agent sees the wrong project, or none
- Troubleshooting"You don't have permission"
- TroubleshootingThe GitHub check fails on my pull request
- TroubleshootingTest results don't show up on the criteria