Connect your Claude Code session
Use your own Claude Code session to pull approved uncapped work and return drafts for review.
The current connection uses Claude Code running in a session you start.
uncapped never receives your Anthropic login or API key in this flow.
How the connection works #
- Your uncapped onboarding owner prepares a private workspace for your account.
- The workspace contains a personal connection token stored in a mode-600 configuration file.
- You keep that workspace private and open Claude Code inside it.
- You ask Claude Code to work your uncapped queue.
- The session leases one authorized task, performs the work, and submits a draft.
- You approve, revise, reject, or cancel the result in uncapped.
The token is stored as a hash by uncapped and can be revoked.
Its permissions cannot exceed the account and venture grants of the user it belongs to.
What the connection can reach #
The connection can receive queued task context that your account is authorized to use.
It cannot read the private journal, another user's ungranted work, uncapped's internal prompts, or the orchestration corpus.
Current limits #
- The session runs only while you have started Claude Code.
- Nothing is scheduled or unattended.
- Workspace setup is support-assisted during the controlled beta.
- Your Claude plan's usage limits still apply.
If a token or workspace may have been exposed, stop using it and contact beta support.