Governed AI agents for engineering teams.

Cody runs on your infrastructure, for the tasks you define, under the rules your team sets.

See use cases Request access

Cody

06:04Updated package dependenciesin acme/portfolio-apichore(deps): bump pg 8.11.3 to 8.12.0CI passingChecks passed
09:12Reviewed a pull requestin acme/payments-api#482 Retry timed-out transfersBreaks PAY-014 at payments/retry.ts:47Changes requested
09:55Investigated an incidentin #supportEU client statement exports stuckDeploy a1c9e2f changed the storage regionEscalated OPS-2291
11:30Ran end-to-end testson PR #512transfer.e2e Scheduled transfers6 of 6 steps passed, recording attachedPassed
14:05Optimized observability costDrop unused account_id tag from portfolio.valuation.durationPull request opened, no monitor reads the tagAwaiting review

Works with the tools you already use

Codexagent

Claude Codeagent

Cursoragent

GitHubsource

Microsoft Teamschat

Jirawork

Datadogsignals

Snyksecurity

Use cases

Work you can hand to Cody.

From pull request review to incident triage, each workflow starts where the work arrives and reports back in the same place.

Request access →

Pull request#482 Retry timed-out transfersOpenChanges requested

payments/retry.ts+9 −2

44 export async function retryTransfer(attempt: TransferAttempt) {

45 return bank.submitTransfer({

46 amount: attempt.amount,

47+ key: crypto.randomUUID(),

48+ timeoutMs: 8_000,

49 })

payments/transfer.tsretries on timeout

18 for (let i = 0; i < 3; i++) {

19 try { return await retryTransfer(attempt) }

20 catch (err) { if (!isTimeout(err)) throw err }

21 }

Codycommented on line 47Major

rules/payments.mdPAY-014Retries must reuse the original idempotency key.

This line creates a new key for each attempt. The caller retries up to three times on a timeout, so a slow bank call can send the transfer twice.

Suggested change- key: crypto.randomUUID(),+ key: attempt.idempotencyKey,

PR review

Cody reviews each pull request against your team's rules and comments on the lines that break them.

HOLD-318Advisor CSV exportTo doSpec approvedIn review

#product

Nadia

@cody draft a PRD: let advisors export client holdings to CSV

Cody

Draft ready in prd.md. One open question for you.

prd.md Approved

# Advisor CSV export

Advisors export the holdings table they are looking at.

Open question: include closed positions?

spec.md Approved

AC-2 Export only rows matching the current filters

Cody opened a pull request

feat(holdings): CSV export for advisor view

holdings/export.go+42
rows := filter.Apply(holdings, req.Filters)AC-2
holdings/export_test.go+36
TestExportRespectsFiltersAC-2

Idea to PR

Cody turns a request into a PRD, a spec and a pull request your team approves.

Pull requestsacme/portfolio-apiScheduledRunning3 open

ScheduleMon 06:00chores/weeklyCody

chore(deps): bump pg 8.11.3 to 8.12.0+2 −2Checks runningAwaiting review
fix(test): wait for valuation-ready in statements.spec.ts+1 −0Checks runningAwaiting review
chore(reporting): drop unused formatQuarter+0 −18Checks runningAwaiting review

e2e/statements.spec.ts+1 −0

22 await openStatement(page, '2026-Q3')

23+await page.getByTestId('valuation-ready').waitFor()

24 await page.getByRole('button', { name: 'Download PDF' }).click()

$ pnpm e2e statements --repeat 20 20 of 20 passed

Cody Skipped lodash 5.x: 14 call sites use removed _.pluck. No PR opened.

Maintenance

On a schedule, Cody opens small pull requests for the chores nobody plans.

Slack#supportThread

Lena 09:52

Client statement exports for EU accounts are stuck since 09:40.

Cody

Investigating with read-only access

Runbook RB-112 does not cover this. statement-worker errors started at 09:38.

09:38:04 ERROR PutObject statements-eu: PermanentRedirect09:38:11 ERROR PutObject statements-eu: PermanentRedirecta1c9e2f region: eu-west-1 → us-east-1

deploy a1c9e2f · 09:36statement-worker errors

Escalated as OPS-2291 with the logs and the diff.

Support and incidents

Cody investigates failures with read-only access and hands on-call the cause.

MetricsCustom metrics by cardinality

Metric	Top tag	Series
`portfolio.valuation.duration`	account_id	182k
`trade.execution.latency`	trade_id	41k
`statement.render.time`	template	3.2k

Queries that read account_id14 monitors, 3 dashboards

monitorp95:portfolio.valuation.duration{env:prod} by {region}no account_id
monitoravg:portfolio.valuation.duration{service:portfolio-api}no account_id
dashboardValuation latency: avg by {service}no account_id

account_id is used by

0 monitors

1 dashboard (groups by service only)

observability/metrics.yamlDraftPR opened

- tags: [service, region, account_id]+ tags: [service, region]

Cody chore(metrics): drop account_id tag from portfolio.valuation.duration

Cost

Cody finds costly metric tags that nothing reads and opens a pull request to remove them.

New tabapp.example.test/transfers/new

Acme WealthTransfer funds

FromBrokerage ••4821

To accountSavings ••1093

Amount€2,500.00

Confirm transfer

Transfer scheduledReference TR-20419Amount €2,500.00

PR #512 transfer.e2eRunningPassed

goto /transfers/new
select to account
fill amount
click Confirm transfer
expect confirmation
expect amount €2,500.00

6 of 6 steps passed

Cody Recording attached to PR #512. Nightly 02:00 run also passed 6 of 6.

End-to-end testing

Cody drives your app in a real browser and reports the result on each pull request and in a nightly run.

Repocody/workflows/release-notes.yamlRunRunningPR opened

kind: Workflowname: release-notestrigger: schedulestages:  - name: collect-merged-prs  - name: draft-notes    dependsOn: [collect-merged-prs]

collect-merged-prsRunningDone
draft-notesRunningDone

Your use case

Bring the work your team repeats

The use cases above are starting points. Any recurring engineering job, such as release notes, schema migrations or on-call handover, can become a Cody workflow, kept in your repo and reviewed like code.

Request access →

Multiplayer

One session your team can share.

Start a Cody session in your chat, your source control or the terminal, and let teammates with access join from theirs. Every question and answer stays in the same session.

Request access →

Start where the work is
A pull request marked ready for review, a chat mention or a terminal command starts the session, with the code and access attached.
Join with the full history
Teammates join from Slack or Microsoft Teams, from GitHub, GitLab or other source control, or from the terminal or web app, and see every question and finding so far. Cody replies where each question came from.
Access follows your permissions
Only people with access to the repository or project can join. Sessions follow your repository and workspace permissions.

Session cdy_1842 · acme/payments-apiReviewingChecks passed

AccessPeople with access to acme/payments-api

MayaGitHub
Marked #1842 ready for review. Please check the retry path.
Codyon #1842 and in Payments Platform
Reviewing the changes in payments/retry.ts. Findings go on the pull request.
Nadia joined from Microsoft Teams · has access to acme/payments-api
NadiaTeams
@cody does a retry keep the idempotency key after a timeout?
Codyin the Teams thread
No. retry.ts:47 creates a new key for each attempt, which breaks rule PAY-014. A slow bank call can send the transfer twice.
Request from the General channel declined: no access to acme/payments-api
Omar joined from the terminal · has access, full history loaded
OmarTerminal
Add a regression test for the timeout case, then fix it.
Codyin the terminal, on #1842 and in Teams
Added TestRetryKeepsKey and reused attempt.idempotencyKey. Checks pass.

Enterprise

Agentic engineering built for the enterprise.

Each workflow names what it can read, what it may change, where it runs and when a person reviews its work.

Request access →

Gitworkflows/dependency-sweep.yaml

acme/portfolio-apiRead and write
acme/payments-apiNo access
Run CI checksAllowed
Open a pull requestAllowed
Merge to mainNot allowed

Access set per workflow

Each workflow lists the repositories, tools and actions it may use, and nothing else.

Session run_01JDX70K2MIsolated

Job: Review PR #482
Repository: acme/payments-api
Workspace: New for this job
Shared with: No other job

One sandbox per job

Each job runs in its own isolated session, apart from every other job.

SlackOPS-2291 statement exports

Read logs and metricsAllowed
Post findings in #supportAllowed
Restart statement-workerNeeds approval

CodyWaiting for an on-call engineer to approve

Changes wait for review

Investigations start read-only, and riskier actions wait for a person to approve them.

Audit logrun_01JDX70K2M

09:12:04CodyStarted run from PR #482
09:12:09CodyRead payments/retry.ts
09:12:31CodyModel call via private-route
09:14:52CodyChecks passed, 3 of 3
09:15:10CodyOpened pull request #486
09:15:11CodyRequested approval from Maya
09:41:27MayaApproved pull request #486

Audit log for every run

Each run keeps its trigger, tool and model calls and checks for review.

Cody

Control planeWorkflows, runs, evals

Cody ModelsModel access and routing

Outbound mTLSNo inbound path

Your cloud

Agent runtimeSandboxed agent sessions

Private gatewaysOutbound to Cody

Private systemsCode, CI, internal tools

Managed BYOC

Agent sessions run in your cloud.

Sandboxed agent sessions, private gateways and private systems stay in your cloud. Cody operates the platform, and your cloud connects to it outbound only.

Cody

Control planeWorkflows, runs, evals

Cody ModelsModel access and routing

Agent runtimeSandboxed agent sessions

Outbound mTLSNo inbound path

Your cloud

Private gatewaysOutbound to Cody

Private systemsCode, CI, internal tools

Fully managed

Agent sessions run with Cody.

Cody runs the sandboxed agent sessions. Private gateways and private systems stay in your cloud and connect to Cody outbound only.

How it works

Every job runs the same way.

Each workflow is a set of files in your Git repository. Cody reads the files, starts a sandbox in your cloud and runs the agent and model they name.

Request access →

HARNESSCodex0.150.1

MODELGLM5.3OpenRouter

Frequently asked questions

Private beta

Bring one job to the private beta.

Cody is available to a limited number of engineering teams. We start with one recurring job and run it on your repositories, tools and rules.

Choose the first job
A recurring task with a clear trigger and an owner who reviews the work.
Set access and checks
Decide which repositories and tools Cody can use and which checks must pass.
Review the first runs
Your team reviews the first runs and reports, then decides what to add next.
RunsFirst week
- statement-worker queue lagSteps posted
  Mon 02:14 Matched runbook RB-112, posted steps
- statement-worker errorsEscalated
  Wed 09:38 Escalated OPS-2291 with logs and deploy diff
- payments-api 5xx rateNo action
  Thu 22:05 No action, alert auto-resolved
- payments-api latencySteps posted
  Fri 07:50 Matched runbook RB-118, posted steps
Reviewed by Platform on-call

See Cody on your first job

We walk through how Cody would run it, what it would access and what it would report.

Request access

Governed AI agents for engineering teams.