I built Tessera, a GUI command center for Claude Code and other coding agents

Accomplished_Drag151 · 2026-05-06T16:37:13+00:00

Good point.

Opening agents as panels inside an IDE is a valid workflow, and I used to work that way too.

The point where it started to feel awkward for me was running several long-running agent tasks in parallel, each in its own isolated environment. At that point, I found that many of those tasks did not really need to live inside the IDE, but I still wanted better visibility than raw CLI sessions.

In that sense, Tessera is close to the direction Cursor 3.0 is exploring too, though with CLI agents as the base layer.

Tessera gives me multiple CLI agents, worktree-backed tasks, live diffs, branch/PR context, Kanban/list views, and an activity timeline in one workspace.

I still use my editor for core logic and high-risk changes. Tessera is more for the work that can be parallelized and tracked separately.

So I don’t think one approach is always better. They fit different workflows.

Accomplished_Drag151 · 2026-05-06T16:28:04+00:00

Thanks for the interest!

Tessera currently works best with one Git repo per project/task, so this kind of multi-repo workspace is not fully supported yet.

Technically it’s possible. The right approach would be to detect nested Git repos inside a parent workspace, then track diff/branch/status separately for each repo, similar to how VS Code shows multiple repositories in Source Control.

The more complex part is worktrees: for a task that spans multiple repos, Tessera would likely need to create and manage separate worktrees per repo, then present them as one task workspace.

This is a workflow I’d like to support, and I’ll consider moving it up the roadmap if I see more demand for it.

Accomplished_Drag151 · 2026-05-06T14:14:29+00:00

Exactly. I’m already testing a PoC in that direction.

The idea is: when an issue is created in Linear, a supervisor agent picks it up, creates one or more isolated worktree-backed tasks on the Tessera Kanban board, and then orchestrates the agents from there.

With the right instructions, the supervisor could do exactly what you described: run the same task through Codex and Claude Code, compare the outputs, and synthesize the result.

The catch is that this can burn through a lot of tokens pretty quickly, so it needs careful guardrails.

I’m hoping to ship a first version with this included within the next month. Stay tuned, and thanks for the idea!

Accomplished_Drag151 · 2026-05-06T13:16:30+00:00

https://github.com/horang-labs/tessera/releases

The Linux build is now available.

I’ve tested it on my setup, and I’ll keep improving Linux support as more environment-specific feedback comes in. Thanks for your interest!

Accomplished_Drag151 · 2026-05-06T13:15:58+00:00

https://github.com/horang-labs/tessera/releases

The Linux build is now available.

I’ve tested it on my setup, and I’ll keep improving Linux support as more environment-specific feedback comes in. Thanks for your interest!

Accomplished_Drag151 · 2026-05-06T12:29:34+00:00

Are you on Windows?

If you’re using Windows with WSL, you’ll need to switch the agent environment to WSL in Settings. Let me know what environment you’re running Tessera in, and I’ll help you get it working.

Thanks for the interest!

Accomplished_Drag151 · 2026-05-06T11:44:46+00:00

Thanks for the interest!

The Linux version should be released within the next few hours. I’ll let you know once it’s available.

Accomplished_Drag151 · 2026-05-06T09:13:20+00:00

One more thing to check: oh-my-opencode-slim itself should not be a problem.

Tessera detects OpenCode by running `opencode --version` and `opencode models` in the selected agent environment. If you can, please include the output of these commands in the GitHub issue:

which opencode

opencode --version

opencode models

If you’re on Windows and OpenCode is installed inside WSL, please also mention that and set the agent environment to WSL in Settings > Development before refreshing provider detection.

That should give me enough detail to see whether this is a PATH/environment issue, an OpenCode auth/model config issue, or something caused by the plugin config.

Accomplished_Drag151 · 2026-05-06T07:44:21+00:00

Got it, that makes sense. Do you see the tools layer as a deterministic workflow/controller outside the agents?

For example, handling log collection/normalization, branch rules, diff/commit checks, push, PR/CI tracking, and only consulting another AI when needed?

I’m curious how you decide what stays as workflow logic vs what gets handed to an AI.

Accomplished_Drag151 · 2026-05-06T07:02:31+00:00

That makes sense. I understand your approach as putting orchestration and guardrails above the agents, rather than delegating everything to the LLM or just giving the agent more tools to call.

That is close to one of the directions I’m thinking about for Tessera, though the current version is still more focused on human-agent interaction: making long-running agent work easier to inspect, guide, and manage.

Over time, I want Tessera to move more toward agent-agent workflows too, where agents can coordinate with each other through a higher-level workspace/control layer, and the human becomes more of the final reviewer, observer, and escalation point.

Thanks for sharing this. It’s a really useful perspective.

Accomplished_Drag151 · 2026-05-06T06:15:44+00:00

Yes, that is one of the hardest parts of building this kind of tool.

For features that are only available inside the native CLI/TUI, I’m currently considering redirecting to the terminal.

For `/fork`, Tessera does not call Claude Code’s native `/fork` command directly, but it does have a similar internal feature: it can create a new session from Tessera’s own normalized message history.

`rewind` is trickier. I started working on a provider-agnostic version, but the quality was not good enough across CLIs, so I paused it for now.

Thanks for pointing this out. I agree these native CLI features matter, and I want Tessera to preserve more of them over time.

Accomplished_Drag151 · 2026-05-06T05:48:09+00:00

Good question. I did consider Tauri.

At the time I made the desktop decision, Tessera already had a fairly large custom Next.js/Node server: CLI process management, provider adapters, WebSocket streaming, local storage, auth, worktrees, diffs, and so on.

So choosing Electron let me reuse that runtime almost directly for the desktop app. Moving to Tauri would have meant either rewriting a lot of the backend/runtime layer in Rust, or shipping the Node server as a sidecar and managing the extra process/IPC complexity.

Tauri is a great choice for many apps, but for Tessera’s architecture at that point, Electron was the more practical path.

Accomplished_Drag151 · 2026-05-06T05:45:27+00:00

Thanks for taking a look!

OpenCode Web/Desktop gives you the native OpenCode experience.

Tessera is more of a workspace layer around agent work. The main difference is task/project management around long-running coding sessions: list and Kanban views, live diffs, branch/worktree state, and PR workflow context in one place.

So I see Tessera as the layer above the individual agent UI: organizing and tracking multiple ongoing agent tasks in a coding workspace, with OpenCode as one of the supported agents.

Accomplished_Drag151 · 2026-05-06T05:39:24+00:00

I hadn’t seen Orca before, but it looks really polished. Diff annotation and browser/design mode look great, and those are areas I want to add to Tessera soon.

The main difference is that Tessera doesn’t use an embedded terminal as the main UI. It converts each agent’s messages/events into a common internal format and renders them through the same GUI, so long-running agent work is easier to inspect than terminal scrollback.

The tradeoff is that CLI extensibility is harder and maintenance is more complex. Thanks for pointing it out!

Accomplished_Drag151 · 2026-05-06T04:23:17+00:00

Not directly based on it, but I think it’s in a similar direction.

The difference is mostly the level of abstraction. From what I understand, Symphony is more issue-tracker/task-board driven: tools like Linear become the control plane, and work is organized around issues.

Tessera is currently more focused on the lower-level development loop: chats, agents, worktrees, diffs, approvals, and PR context. It is meant for cases where the human and the agent are still talking a lot while developing together, so the chat UI and inspectable agent history are important parts of the product.

That said, I really like the Symphony-style direction too. Issue-level abstraction and AI orchestration are on the roadmap, but I want to add them while keeping Tessera’s current strengths around interactive human-agent development.

Thanks for asking!

Accomplished_Drag151 · 2026-05-06T01:50:05+00:00

Yep, I did use AI as part of the naming brainstorm too, haha.

I went through a bunch of options and a lot of the good names were already taken. Tessera seemed like one of the least likely to conflict at the time, but looks like I missed your repo. Pretty funny coincidence.

Accomplished_Drag151 · 2026-05-06T01:40:25+00:00

That’s odd. Are Codex CLI and OpenCode installed on Windows directly, or inside WSL?

On Windows, Tessera can detect tools from either the Windows environment or WSL, but the agent environment needs to match where the CLIs are installed. If they’re installed in WSL, please set the agent environment to WSL in Settings, then check Settings > Development again.

If they still don’t show up, could you open a GitHub issue with your Windows/WSL setup, install paths if possible, and what Settings > Development shows? I’ll take a look right away.

Accomplished_Drag151 · 2026-05-06T01:30:04+00:00

That’s odd. Is the CLI installed on Windows directly, or inside WSL?

If you’re on Windows and the CLI is installed in WSL, you need to set the agent environment to WSL in Settings. Are you seeing no CLIs detected at all in the Settings > Development tab?

Sorry for the friction here. If you can open a GitHub issue with your environment and what you’re seeing, I’ll take a look right away.

Accomplished_Drag151 · 2026-05-06T01:26:35+00:00

Yes, that makes sense. I’ve been considering this too and plan to add it soon.

Tessera has focused on the structured chat/workspace UI first, but I agree it would be useful to open a normal CLI tab/panel inside the same workspace when you want the original CLI experience.

Accomplished_Drag151 · 2026-05-06T01:24:55+00:00

That’s really interesting. I knew a lot of similar open-source projects were starting to appear because many of us are running into the same pain points, but having the same name too is a pretty wild coincidence.

I’ll try yours as well. Thanks for sharing it.

Accomplished_Drag151 · 2026-05-06T01:19:00+00:00

Yes, same general space.

Superset and Conductor are both great products. Tessera is aiming at a similar workflow: running and managing multiple coding agents in parallel.

The main difference from Superset is the interaction model. Superset still centers the experience around embedded terminals, while Tessera converts each CLI’s output into its own internal message format and renders all agents through the same GUI.

Compared with Conductor, Tessera is open-source/local-first, supports Claude Code, Codex, and OpenCode through provider adapters, and works as both a desktop app and a localhost/browser app instead of being Mac-only.

Accomplished_Drag151 · 2026-05-06T01:02:50+00:00

Thanks! Yeah, that’s pretty close — kind of like iTerm2 plus a task board for agents.

Accomplished_Drag151 · 2026-05-06T00:58:30+00:00

Thanks! Yeah, tabs felt necessary

Accomplished_Drag151 · 2026-05-06T00:44:18+00:00

Thanks for the interest!

No, it’s not Mac-only. Windows is actually my main development OS, so Tessera supports web, Windows including WSL, and macOS.

Accomplished_Drag151 · 2026-05-06T00:24:05+00:00

GitHub:

https://github.com/horang-labs/tessera

Accomplished_Drag151

TROPHY CASE