Thanks to visit codestin.com
Credit goes to github.com

Skip to content

kyashrathore/Claxedo

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

9,440 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Claxedo

A clean fork of OpenCode Desktop for running many agents at once.

Why Claxedo?

  • Any project, any workspace — tabs are flat (not nested), so switching between projects and worktrees is fast and easy.
  • Any agent, your own subscriptions — use Claude, Codex, Gemini, or any CLI agent with first-class terminal support and notifications to track work state.
  • Process management that carries over — set up processes once, keep them consistent across worktrees, and soon query logs by process name.
  • File manager across the workspace — unlike OpenCode's session-scoped behavior, files are not scoped to one session; each file opens in its own tab.
  • Code review across worktrees — local review is not session-scoped; each local review spins up a dedicated OpenCode session.
  • Port-conflict handling built in — use integrated Portless proxy support to avoid manual port juggling.
  • Themes, keybindings, plugins, and sync — customize the app while staying aligned with upstream OpenCode updates.

Where Claxedo Is Ahead

Area OpenCode baseline Claxedo
Workspace navigation Session-oriented flow can feel nested when juggling many projects/worktrees Flat, non-nested tabs across projects and worktrees for faster switching
Agent workflows Great single-session terminal workflows Built for parallel agent operation with first-class terminal UX and state notifications
Process management Setup often repeated per context Setup once and keep behavior consistent across worktrees; upcoming getLogs("processName") support lets agents fetch logs by process name anytime
File manager scope Session-scoped context Workspace-wide context, and each file opens in its own tab
Local code review scope Session-bound review flow Review across worktrees; each local review starts a dedicated OpenCode session
Port conflicts Manual env/port coordination between tools Built-in Portless proxy support for smoother multi-agent workflows
Customization + sync Upstream defaults Themes, keybindings, and plugins while staying regularly synced with upstream

Feature Demos

Any project, any workspace (flat tabs), Any agent + terminal-first flow + notifications

multi-tab-multi-agent-terminal-first.mov

Process setup once, persists across worktrees, Port conflicts via built-in Portless support

process-management.mov

File manager across workspace

file-manager.mov

Local code review across worktrees

local-code-review.mov

Themes, keybindings, plugins, upstream parity

standard-opencode-features.mov

GitHub Demos (Direct Video Links)

These links open videos directly in GitHub's native viewer.

FAQ

Why not just run agents in raw terminal tabs?

Raw terminal tabs give execution. Claxedo adds orchestration: workspace-aware tabs across projects/worktrees, process-state notifications, review/file-manager flows that are not session-limited, and quick agent launch patterns.

How does process management behave across worktrees?

You set it up once, and the process-management workflow persists across worktrees instead of making you rewire each context.

What is upcoming for process management?

Upcoming support for getLogs("processName") will let an agent target a process by name and inspect its logs at any time.

How does Claxedo handle port conflicts?

Claxedo includes built-in Portless proxy support so multiple local agents/services can run with less manual port coordination.

Which agents does Claxedo support?

Any CLI agent that can run in a terminal workflow, including Claude Code, Codex, Gemini CLI, and custom/internal agents.

Do I need a Claxedo subscription to use agents?

No. Bring your own agent subscriptions or credentials.

Is Claxedo a hard fork from OpenCode?

No. Claxedo uses a file-override approach and stays in sync with upstream OpenCode regularly.

Getting Started

Prerequisites

  • Bun >= 1.3
  • Rust (for desktop builds)

Development

# Install dependencies
bun install

# Start the app in dev mode
cd packages/claxedo-app && bun run desktop:dev

Building

# Desktop build (unsigned, for local testing)
cd packages/claxedo-app && bun run desktop:build

Download

Download from Claxedo v0.0.8.

Platform Download
macOS (Apple Silicon) Claxedo_0.0.8_aarch64.dmg
macOS (Intel) Claxedo_0.0.8_x64.dmg
Windows Claxedo_0.0.8_x64-setup.exe
Linux (Debian/Ubuntu) Claxedo_0.0.8_amd64.deb
Linux (Fedora/RHEL) Claxedo-0.0.8-1.x86_64.rpm

How It Works

Claxedo is built on top of OpenCode using a file-based override system:

  • @/ resolves to src/overrides/* first, then falls back to upstream packages/app/src/*
  • Only the files that need to change are overridden — everything else comes from upstream
  • This keeps merges clean and makes it easy to stay current with OpenCode
packages/
├── claxedo-app/          # Overrides + extensions
│   └── src/overrides/    # File-level overrides of upstream UI
├── app/                  # Upstream OpenCode UI (SolidJS)
├── desktop/              # Tauri desktop shell (Rust)
├── opencode/             # CLI & sidecar server
└── ui/                   # Shared UI components

Releasing

Releases are automated via GitHub Actions.

cd packages/claxedo-app

# Create a release
bun ./scripts/release.ts patch   # 1.1.0 → 1.1.1
bun ./scripts/release.ts minor   # 1.1.0 → 1.2.0

# Push to trigger CI
git push && git push --tags

See RELEASING.md for details.

Contributing

See CONTRIBUTING.md for guidelines. The key rule: keep Claxedo changes in overrides so upstream syncs stay clean.

Tech Stack

  • UI: SolidJS, Vite, Tailwind CSS
  • Desktop: Tauri (Rust + WebView)
  • CLI: OpenCode sidecar (Bun)
  • Build: Turborepo, Bun workspaces

About

The open source coding agent.

Resources

License

Contributing

Security policy

Stars

Watchers

Forks

Packages

No packages published

Languages

  • TypeScript 57.0%
  • MDX 36.5%
  • HTML 2.9%
  • CSS 2.6%
  • Rust 0.4%
  • Astro 0.3%
  • Other 0.3%