Dispatch

Dispatch is a chat assistant that plans work across CodeCargo — agents, workflows, guardrails, CargoWall, projects, and more — then runs that plan only after you approve it. Each plan is an ordered list of steps: some call a specialist agent from your catalog, others perform a platform action such as opening a pull request or running a Self-Service Workflow. Steps share a workspace, so later steps can use what earlier ones produced.

Opening Dispatch

• Navigate to Dispatch in the sidebar, press ⌘I to open it from anywhere, or press ⌘K and jump to it from the command palette. Typing a question into the command palette also works — the Ask Dispatch row hands your text straight to a conversation.
• Start a new conversation, or pick an existing one from the thread rail.
• Plans waiting for approval also appear on the org dashboard and in the Activity pill. The dashboard card shows the plans you can approve — your own, or every waiting plan if you are an org admin.

You can rename or delete a conversation from the thread rail. Deleting hides it from the list; that conversation can no longer receive messages.

What You Can Ask

Tell Dispatch what you want in natural language. It looks up the entities you already have, then answers directly or proposes a plan. Typical requests include:

• Run or create an Agentic Job, or cancel a run already in progress
• Create a project, a Self-Service Workflow, or a CargoWall policy
• Run a Self-Service Workflow, a guardrail evaluation, or a remediation
• Scan repositories with the Service Catalog
• Open a pull request
• Investigate a failure or a compliance finding — investigations run in the background, and the findings arrive in the conversation when they finish
• Show work you own across the organization
• Answer questions about CodeCargo itself — Dispatch can search this documentation

Enabled MCP servers that you have made available to Dispatch can be called as tools during the conversation and from plan steps. For the full, current list of what Dispatch can do, open the capability catalog from the Dispatch page itself.

If you ask Dispatch to pass feedback along, it sends that feedback to CodeCargo. Dispatch also records conversation sentiment to improve the product; organizations can opt out of sentiment capture by contacting CodeCargo.

Plans

When the work needs more than a single answer, Dispatch presents a plan: a title, a short summary, and an ordered list of steps. Each step is either:

• An agent step — a specialist from your Agent Catalog, with a prompt, run as a child of the plan
• A platform step — a CodeCargo action such as creating a policy or opening a pull request

Steps can be conditional: a step can be marked to run only when the previous steps succeed, only on failure, or always — so a plan can include cleanup or recovery steps that take over when an earlier step fails.

One caveat when chaining steps: a step that starts an Agentic Job run is fire-and-forget. The plan does not wait for the job to finish, and later steps cannot use the job's output.

Nothing in the plan executes until you approve it. While a plan is waiting for approval, you can remove a pending step — only pending steps can be removed, and at least one must remain. Only the plan's creator or an org admin can edit it.

Approving or Denying

The approval card shows the steps that will run and any problems Dispatch detected — for example, a missing repository or a step that depends on a branch that isn't ready. Fix or remove the blocked steps, then Approve or Deny. When you deny, you can attach a reason; it is recorded on the plan.

If a step needs repositories that were not in the original scope, Dispatch pauses and asks you to allow those repositories before it continues.

Approvals also show up in the Activity pill and on the org dashboard, so you can decide without hunting through chat history.

Denying is final for that plan — it cannot be edited or resumed afterward. If you want changes, tell Dispatch what to adjust and it proposes a new plan; a denied plan can also be rerun from plan history.

While a Plan Runs

Open the plan to watch each step. Agent steps appear as linked child runs; platform steps record their result on the step itself. You can Cancel a plan that is waiting for approval or already executing. Canceling before approval discards the plan; it is not the same as denying it.

Plan History

From Dispatch, open Plans to browse org-wide history. You can filter by status or search by title. A plan is visible to you when you can access every repository attached to its run; plans with no repositories attached are visible to the whole organization.

From a plan's detail page:

Rerun and resume always ask for a fresh approval before any step executes.