Docs
Beta · biscuit · v0.0.1How to use the IDE
Left bots, center Ask / Plan / Agent, right VM, plus Connections, Projects, and Settings.
The three columns
Orca Cockpit is laid out so chat and the machine stay in the same glance. That is IDE 360 — you always see which bot is selected, what mode you are in, and whether the Project VM is ready.
- Left — bots. Each bot is paired with one dedicated Linux Project. Select a bot before you Ask.
- Center — Ask / Plan / Agent. Same thread, different permission to move.
- Right — the VM and live Project view. Use it when a flow needs a browser, a terminal, or an OAuth click.
Ask, Plan, Agent
Ask
Read-only questions against the live Anypoint estate and the current project. Status, drift, vCores, unpoliced APIs, “what is deployed where.” This is where Sign in drops you.
Plan
Turn a ticket into a sequence: which apps, which runtime, what to touch first. Plan does not apply the change; it makes the steps visible in the panel so you can edit them.
Agent
Carry work through the Mule repo on the Project VM — scaffold, DataWeave, tests, commit. Stay in the project instead of a side chat that cannot see files.
Connections
The Connections panel reflects what the vault hydrated: Cursor, Anypoint, and optional Salesforce, GitHub, and Postman. If a logo is dark, the key is missing or the last hydrate failed — go back to website Settings. You cannot write vault secrets from the IDE.
Projects
Projects also appear on orcaesb.com/access as a read-only list. The website creates your default Project on first account visit. Extra Projects come from Orca Cockpit IDE (POST /api/workspaces). The website does not stop or remove them. Status values you will see: queued, provisioning, ready, error.
Settings (desktop)
Desktop Settings are for app preferences and Sign in / Sign out. Secret values are not edited there. Website /settings is the vault.