Studio

One workspace. Six surfaces over one graph.

Trellis Studio is where you tend the vines: code, history, agents, decisions, and issues on the same substrate. The engine runs by itself. Studio is how you work inside it.

$npx trellis studio

Opens Trellis Studio in your browser. Local-first by default.

Surfaces

Six tools that used to live in five different apps.

Graph, editor, history, agents, decisions, and issues — all reading and writing the same causal graph.

Graph view

Graph view

Entities, ops, and links as a living graph. Click to inspect anything.

Code editor

Code editor

Code entities in a tree. Every change becomes a causal step in the op stream.

History and diffing

History and diffing

View history as a graph, with semantic diffing that understands structure, not lines.

Embedded agents

Agents run inside the workspace. Every tool call is an op, not a chat log.

Decision traces

Decision traces

Capture the why behind every change. Search precedent across past runs.

Issues and milestones

Issues and milestones

Task tracking in the same graph as the code it ships with.

Agent harness

Every tool call is an op, not a chat log.

When an agent runs inside Studio, every tool call emits an op. The chat is the user-facing surface; the op log is the durable record. Asking why did the agent do that? becomes a graph traversal, not an archaeological dig through scrollback.

This breaks the "RAG over chat history" pattern. The agent doesn't have to remember its reasoning by searching its own logs. The reasoning is structured data in the same graph as the code it changed.

Get started

Run it locally

No account. No cloud. No signup. Your project, your machine, your data.

Requires Node 18+ and git.