Coding agent

Take Claude Code from ticket to reviewed pull request

Keep the brief, policy, progress, pull request, review, and acceptance decision on one accountable task.

Join the waitlist See the Claude Code example

Claude Code with Aestus

Keep the tool. Change what the team can see.

Each Claude Code session starts with the Workspace Memory brief and relevant cited claims available to that session. Personal, team, workspace, and organization claims keep their audience rules. At handoff, it can propose what it learned for human review.

Claude Code receives the full card, not a loose prompt. The repository, expected result, dependencies, comments, and artifacts stay attached while it works. Progress remains visible on the task instead of moving to a second status channel.

The handoff returns the pull request to the card that requested it. Checks and acceptance remain separate decisions. The native adapter can pause supported consequential tool calls for approval, and Aestus records who decided and why.

Settings that ship with Claude Code are read by the client, and Anthropic describes managed settings as configuration precedence rather than a security boundary. Aestus Sandboxes moves the whole session onto a machine the developer does not administer: repositories, reachable hosts, brokered keys, tool catalog, permitted models, and budget are decided once by an owner and applied where the process runs.

Good first workflows

Fix a narrow regression
Give the agent failing fixtures, a bounded file area, and an explicit test contract.
Upgrade a dependency
Keep the version change, compatibility proof, pull request, and review on one task.
Implement a migration
Require a dry run, rollback note, and named approval before the consequential step.

A complete Claude Code example, from trigger to proof.

The example names the people, task event, tool boundary, returned evidence, and acceptance state. The run row below it is a fixed product example, not customer data.

Example — fictional team and data. Not a live run or customer result.

Inside the connected tool

What the handoff looks like in Claude Code

The agent reads the task through MCP, claims it, and returns the pull request to the same record.

Example — fictional team and data. Not a live run or customer result.

Developer terminal

Live

claude
sandbox ready · policy "Engineering default" v7 · egress restricted
Claude CodeReading src/billing/invoice.ts
Claude CodeEdit src/billing/invoice.ts
Blocked by policy: api.unknown-host.dev
Claude CodeRan tests · 41 passed

Example — fictional team and data. Not a live run or customer result.

Concrete workflow example

Repair a production import without losing the review trail

A CSV import started accepting malformed currency values. The task names the failing cases, repository, owner, and proof required for acceptance.

TriggerAES-482 moves from Ready to In progress

1
Maya · Product
Attaches the failing samples and acceptance rules
Reject mixed decimal separators without changing valid EU imports.
3 samples · 2 required checks
2
Claude Code
Claims the task and reports the implementation phase
Reads the full card, traces the validator, and changes only the parser boundary.
claim · progress: implementing
3
Claude Code
Returns a pull request with focused tests
Adds the malformed fixtures and keeps the existing valid-import matrix green.
PR #184 · 19 tests passed
4
Maya · Product
Accepts the result after review
The acceptance decision stays beside the brief, run cost, checks, and pull request.
accepted · receipt 7f4a…c19e

Example — fictional team and data. Not a live run or customer result.

Deterministic product example — not a production run

Patch the import validator

Example run		Runtime	Outcome
EXAMPLE-CC-01	Claude Code	claude-code	Completed	$0.03	12.1s

Tokens in / out: 4,800 / 300
Failure code: —
Agent: coding-agent

Example source: lib/marketing/integration-run-examples.ts

Example run cost

$0.0317 in the deterministic product example

This complete checked-in example defines one consistent identity, runtime, outcome, token count, duration, and cost. It is not a production run or a promise about your workload.

Set it up in four steps.

Follow the real Claude Code connection path. Provider steps link to the provider documentation. Aestus steps name the contract they follow.

01
Add Aestus as a remote MCP server
Register the Aestus Streamable HTTP endpoint from a terminal.
claude mcp add --transport http aestus https://aestus.app/api/mcpRead the provider docs
02
Complete OAuth in Claude Code
Open /mcp, select Aestus, and finish the browser sign-in and consent flow.
/mcpRead the provider docs
03
Work one card end to end
Read the brief with get_task, claim the card, report each changed phase, attach the pull request, then release it for review.
Aestus contract: docs/agent-ticket-workflow.md
04
Run it governed in early access
Aestus provides the sandbox CLI and setup path during early-access onboarding. It starts Claude Code remotely while your terminal stays local.
Aestus contract: docs/runbooks/aestus-cli.md

The boundary stays visible while the work moves.

See what Claude Code can do, where a person still decides, and what Aestus records for every governed run.

Where control lives

Native approval support

The Claude Code adapter can pause a run for Aestus approval gates.

Consequential actions stay named

Pull request open, pull request merge, destructive command, external write, and policy bypass can require a person.

The board owns the decision

The approval, actor, reason, and resulting action stay with the task instead of disappearing into a terminal transcript.

What Aestus records

Usage

Input tokens, output tokens, model spend, and tool spend are recorded for the run.

Time

Run latency and step timing show where the work waited, retried, or failed.

Outcome

Completion, acceptance, and a stable failure code such as checks_failed remain queryable.

Questions teams ask

Does Aestus replace Claude Code?

No. Claude Code does the coding work. Aestus supplies the shared task, policy, progress record, approvals, and handoff.

Can Claude Code ask for approval during a run?

Yes. The Claude Code adapter supports Aestus approval gates for actions covered by the active policy.

Can Claude Code run somewhere other than my laptop?

Yes, for teams in Aestus Sandboxes early access. The session runs on a remote machine your organization defines, with its repositories, network, credentials, tools, models, spend, and record set there.

See all integrations See the security controls

Start with one Claude Code run.

Bring one real run. Map its actors, boundary, evidence, cost, and acceptance step.

Talk to us

Example — fictional team and data. Not a live run or customer result.

Concrete workflow example

Repair a production import without losing the review trail

A CSV import started accepting malformed currency values. The task names the failing cases, repository, owner, and proof required for acceptance.

TriggerAES-482 moves from Ready to In progress

1
Maya · Product
Attaches the failing samples and acceptance rules
Reject mixed decimal separators without changing valid EU imports.
3 samples · 2 required checks
2
Claude Code
Claims the task and reports the implementation phase
Reads the full card, traces the validator, and changes only the parser boundary.
claim · progress: implementing
3
Claude Code
Returns a pull request with focused tests
Adds the malformed fixtures and keeps the existing valid-import matrix green.
PR #184 · 19 tests passed
4
Maya · Product
Accepts the result after review
The acceptance decision stays beside the brief, run cost, checks, and pull request.
accepted · receipt 7f4a…c19e

Example run

Runtime

Outcome

EXAMPLE-CC-01

Claude Code

claude-code

Completed

$0.03

12.1s

Questions teams ask

Does Aestus replace Claude Code?

No. Claude Code does the coding work. Aestus supplies the shared task, policy, progress record, approvals, and handoff.

Can Claude Code ask for approval during a run?

Yes. The Claude Code adapter supports Aestus approval gates for actions covered by the active policy.

Can Claude Code run somewhere other than my laptop?

Take Claude Code from ticket to reviewed pull request