v0.3.0Free and open source

Keep up with your agents.

CodeTrellis is observability for AI coding agents. See what they change, check it against the plan, and correct or steer them as they work, from one agent to a whole team.

Download for macOS

macOS, Windows and Linux · Apache 2.0 · No telemetry

MCP tools your agents can call
212
MCP tools your agents can call
languages parsed, plus SQL in strings
11
languages parsed, plus SQL in strings
MCP agent: Claude Code, Codex, Cursor and more
Any
MCP agent: Claude Code, Codex, Cursor and more
telemetry. Not a setting: it isn't built in
None
telemetry. Not a setting: it isn't built in
free, with the source public
Apache 2.0
free, with the source public

Scales with you

One agent, a few, or a whole team.

Start with one agent you want kept on track. Add more, then your teammates. It's the same app at every step.

Line history naming codex as the agent that wrote a line, with a drifted line flagged.

Every line has an author.

See which agent wrote a line and the commit it landed in. A change no task asked for is marked as drift, right on the line.

Map

However large the codebase.

Open a repository and get its dependency graph: packages, files and how they connect, live as the code changes.

The dependency graph of a 1,509-file repository, live.

Plans

A plan your agents work from.

Break the work into tasks. Agents claim them, and you see who has which, how far along each one is, and every status as it lands.

A plan's tasks being claimed by agents, with progress bars and statuses landing in the Activity feed.

Many agents at once

Two agents reached for the same function.

Every worktree and branch is a line of work. When two of them change the same function, it's flagged high, both are named, and the agent is told.

An overlap flagged high: auth-refresh and billing-v2 both change isValidEmail, and codex is told.

Steer and protect

Ask me before you change that.

Put a breakpoint on code that matters. When an agent goes to change it, the edit isn't made until you answer: continue, continue with a note to steer it, or stop.

Answer at your desk, or on your phone.

A breakpoint holds Claude Code's edit to validators.ts until Continue is pressed.
The same breakpoint on the phone: Continue, Continue with steer, or Stop.

Review

Check it did what you asked.

Every changed line is checked against the plan. A change no task called for is flagged as drift, on the line where it happened.

A changed line in config.py flagged as unexpected drift against the plan.

Architecture rules

Write the rule once. CI holds it.

Say which part of the code may not import another, and why. Agents are told before they write an import that breaks it, and codetrellis check fails the build when one gets through.

The architecture rule in Settings: services/api/app/routes/ may not import services/api/app/config.py, because routes read settings through the app.
The rule in Settings, with its reason.
CI · branch exports-v2

Ran codetrellis check --base main. Output: Does not conform (1 changed file since main): ✗ services/api/app/routes/users.py now imports services/api/app/config.py, which the rule “services/api/app/routes/ may not import services/api/app/config.py” forbids: routes read settings through the app Exit code 3.

Ran codetrellis check --base main. Output: Conforms: 1 changed file since main. No breakpoint holds them, none of their tests fail or are older than the code, no done task fails its checks, no doc that describes them is stale, and they add no import an architecture rule forbids. Exit code 0.

A recorded run: the check fails on the breach, then passes once it's fixed. The output is exactly what the tool printed.

More to explore

There's more in the window.

Catch up in a minute

Every active line of work, and which overlaps are waiting on you.

See the lines

The file, with the lines each line of work changed in it.

Replay

Scrub the project back to an earlier moment and see it as it was.

Freeze for release

Freeze the project with a reason: release 2.3, fixes only.

Recurring playbooks

A weekly review comes due and asks whether to start it.

Tests as evidence

A criterion carries its test report. Failing, it waits for you to approve or send back.

What to merge first

A suggested merge order, with the reason for each place.

You sign off

An agent offers evidence. A person marks the criterion met.

A record you can check

Settings confirms the record is intact: every entry matches the chain.

On your phone

A changed signature, and the agents waiting on your answer.

Security and privacy

Your code stays yours.

CodeTrellis runs where your code is, and every way in is closed until you open it.

Read the source, Apache 2.0
  • Runs on your machine

    The only request the app makes on its own is the update check, and Settings → Updates turns that off.

  • Every connection authenticated

    Each local connection, from the app, an agent or the API, carries a token minted for that launch.

  • Remote access off by default

    Nothing is reachable from outside until you turn it on. Being discoverable is a separate switch from being exposed.

  • Phone pairs peer to peer

    Your phone talks to your desktop directly over WebRTC, with no central server. For remote use, bring your own VPN.

  • Signed releases

    Downloads are verified against a signed release manifest.

  • Agents allowed tool by tool

    You grant each tool. One you haven't granted is refused, by name.

Download · v0.3.0

Keep up with your agents.

Free and open source. Your code stays on your machine.

CodeTrellis-0.3.0-arm64.dmg · 323 MB

Windows

Windows builds aren't code-signed yet, so SmartScreen may warn the first time you run one. The download is still checked against the signed release manifest.

Linux

Prefer .deb or .rpm where your distribution takes one: they keep Chromium's sandbox, which the AppImage runs without.

Every release, with checksums, is on GitHub. The phone companion is on the downloads page.