A teammate who can open every system you connect, and never changes anything without asking you first.
Why does the order-sync flow call the warehouse API twice?
The retry policy does not reuse the idempotency key, so the second call looks like a new order. I can draft the fix for the DataWeave mapping.
Ask in plain English
Answers come from the systems themselves: objects, flows and Apex in your org, APIs and applications in Anypoint, issues and pull requests in your repositories. Each connection acts as you, so the Copilot only sees what you can see.
Approval needed (example)Update one Account recordLands in: Salesforce, Production mode, org Example CorpChange: Billing city, Austin to DenverApproveDeny
Nothing changes without you
A change becomes an approval card that shows the exact change and where it lands: which org, which workspace, which repository. Approve and the brain checks your mode again, then applies it. Deny and nothing is written.
Asleep: wakes when you chatYour Workstation1Build the project2Run the tests3Open the pull request, after you approve
A computer of its own, asleep until needed
Your Workstation is a private machine in the cloud where the Copilot builds and tests code. It sleeps when you are not chatting, shows its state on one page, and stops by itself when your monthly hours run out.
The rules are enforced on the server, not only on screen.
01
Sandbox is read-only
A new account starts in Sandbox. In Sandbox the Copilot is not offered any write tool. This is Cockpit declining to write; it is not a read-only credential at the provider.
02
Production writes need approval
Every write waits on a card that names exactly where it lands.
03
Credentials are encrypted
The access Cockpit holds for your tools is stored encrypted. Disconnecting a tool deletes Cockpit's copy, and for Salesforce, Slack and GitHub also revokes the grant at the provider.
04
One AI provider
Anthropic is the only AI provider. The Copilot runs on Claude.
05
Text from your tools is data
What the Copilot reads from Slack, GitHub, Postman and Anypoint is marked as data, not as instructions from you.
06
You can leave
Delete your account in the app, and your data and your stored connections go with it.
Meet the flight crew
Every part of Cockpit has a call sign. Each card says what that part does and what it is not allowed to do.
Copilot
Call sign: Muse
Reads the systems you connected and drafts the change.
Cannot: write anything without an approval card.
Captain
Call sign: Skipper
The admin. Invites the Crew and chooses who may use which connector.
Cannot: read a member's chats.
Architect
Crew member
Leads the integration design and approves their own writes.
Cannot: approve anyone else's change.
Developer
Crew member
Builds in a sandbox first and ships when the card says yes.
Cannot: write anywhere while in Sandbox mode.
Take it from here.
Cockpit is invitation-only while we grow. Join the waitlist and the founder will write to you personally.