Alethe

The multi-agent coding workspace.
Run Claude Code, Codex, Copilot and your shells side by side — in one local-first desktop app.

Download · Report Bug · Request Feature · Security · Privacy · Contribute

[!IMPORTANT] Alethe is an early public release. The desktop app is free, open source, and local-first, not local-only: update checks and provider usage polling are on by default, while other network features are optional or action-triggered. Manual GitHub Gist Sync is already available; first-party hosted sync or cloud backup may be offered separately later. See the privacy and data-flow guide.

What Alethe Is

One agent in one terminal is easy. Five agents across three repositories is the actual job — and that is where terminal tabs stop working: sessions get lost, MCP servers drift out of sync between agents, and nobody knows which agent is doing what, where.

Alethe is a desktop workspace built for that. Every agent runs in a real PTY inside a persistent project layout, keeps its own session and history, and stays alive when you rearrange the UI. On top of that, Alethe manages the things agents share: their CLIs, their MCP servers, their skills, and the conversations you move between them.

Cross-platform (Windows, macOS, Linux), local-first, built with Tauri, Rust, React, and xterm.js. “Local-first” describes workspace persistence, not an internet-free guarantee; see docs/PRIVACY.md for current network defaults, credentials, and retention.

Supported Platforms

macOS	Windows	Linux
Available on macOS	Available on Windows	Available on Linux

Agents

Missing CLIs can be installed, updated, and uninstalled from inside Alethe — it probes the machine for Node, npm, WinGet, Scoop, and Chocolatey and offers only the methods that actually work there, preferring each vendor's official installer. Already-installed CLIs are discovered across PATH, registry, npm/pnpm/Volta/fnm/nvm/Bun/Cargo/Scoop/Chocolatey, and can be pointed at a custom path.

What It Does

Run agents in parallel

• Projects, groups, and subgroups organize repositories; each open project becomes a container with its own panes.
• One agent per pane, or several agents as sub-tabs inside the same pane — each with its own PTY, working directory, and session.
• Auto, spotlight, sidebar, and custom grid layouts, editable directly on the grid.
• Closing a container hides it; the process keeps running.

Keep the context

• Sessions of Claude Code, Codex, and OpenCode resume after a crash or a restart.
• Recent chats lists the conversations of a pane's working directory and reopens any of them.
• A Claude Code conversation can be handed off to Codex (and back) through a locally redacted context packet — no copy-pasting the thread by hand. Redaction is best effort, so review the packet before starting the target agent.
• Scrollback is persisted per PTY, so reattaching shows what happened before.

Manage what the agents share

• MCP tab: every MCP server configured on the machine, grouped by server and showing which agents have it — read from Claude Code, Codex, OpenCode, and Antigravity configs. Add, remove, copy a server from one agent to another, search the official registry, and ask each agent to verify it can really reach a server. Every write is backed up, re-parsed, and committed atomically.
• Skills tab: the skills installed for each agent, with links and shared stores resolved so a shared skill shows up once.
• Graphify: a code graph of the project, served to the agents as an MCP server.

Stay in control

• RAM readout in the title bar; disable a terminal or suspend a whole group to get memory back.
• Git panel per project — status, stage, commit, branches, diffs in a pane — plus worktrees for parallel tasks.
• Content panes beside the terminals: file explorer, Markdown, diffs, images, video, embedded browser.
• Todos per project, isolated profiles, local backup export/import, 14 UI and terminal themes, EN and pt-BR.
• Remote Control: an authenticated LAN web view, paired by QR code, to follow and answer agents from your phone. It is off by default and uses unencrypted HTTP/WebSocket transport on the LAN, so enable it only on a trusted network. Clean profiles are read-only; answering agents requires a separate input opt-in, and shell input has its own additional opt-in.
• Spotify Now Playing, using your own Spotify app credentials in Preferences ▸ Spotify with http://127.0.0.1:8888/callback as the redirect URI. Current releases store those credentials in local profile files; see the privacy guide before exporting or sharing profile data.

Core Concepts

Product Philosophy

A focused core with optional capabilities, closer to Obsidian than to a maximalist IDE. Non-essential features ship behind feature flags or opt-in settings, and a clean installation stays a first-class experience. Coherence over volume.

Install

Use the published installers from Releases.

[!WARNING] Windows builds are not code-signed yet, so Defender may flag alethe.exe as Trojan:Win32/Bearfoos.A!ml and quarantine it. The !ml suffix denotes a machine-learning heuristic rather than a publisher signature, and terminal-multiplexer behavior such as spawning child processes and creating PTYs can produce false positives. Verify that the download came from the official Releases page; do not bypass a warning for an artifact from another source.

To recover it: Windows Security → Virus & threat protection → Protection history → Actions → Restore, then add an exclusion for %LOCALAPPDATA%\Alethe (and src-tauri/target if you build from source). Reports of incorrect detection go to Microsoft Security Intelligence. macOS builds are not notarized yet either — right-click the app and choose Open to bypass Gatekeeper. Signing and notarization are on the roadmap.

Run From Source

git clone https://github.com/Kc1t/alethe-agents.git
cd alethe-agents
npm install
npm run app

Requirements: Node.js 18+, Rust stable, Visual Studio Build Tools on Windows, Tauri system dependencies on Linux:

sudo apt install -y libwebkit2gtk-4.1-dev libappindicator3-dev librsvg2-dev patchelf

npm run app          # desktop app with hot reload
npm run dev          # frontend only
npm run build        # typecheck + build frontend
npm run tauri build  # installers → src-tauri/target/release/bundle/

Terminal Command

Install the alethe command from Settings ▸ Integrations ▸ Terminal command:

alethe                # opens the current folder as a project
alethe ~/some/project # opens the given folder

If the folder is already a project, it is brought into the workspace instead of duplicated. If Alethe is already running, the existing window is focused. The command lands in ~/.local/bin/alethe (macOS/Linux) or %LOCALAPPDATA%\Alethe\bin\alethe.cmd (Windows) — reinstall it after moving the app.

Roadmap

• Multi-agent workspace with projects, groups, containers, and sub-tabs.
• Real PTYs with spawn, attach, resize, scrollback, and session resume.
• Agent install/update/uninstall, MCP and skills management.
• Releases for Windows, Linux, and macOS.
• Windows release signing and macOS notarization.
• Broader Linux/macOS validation on real machines.
• First-party hosted cloud sync/backup (manual GitHub Gist Sync is already available).

Contributing

Contributions are welcome. Read CONTRIBUTING.md for setup, project layout, and house rules. The easiest ways to help:

• Pick an issue labeled good first issue or help wanted — comment to claim it.
• Report a bug with clear reproduction steps, or request a feature with the workflow it improves.
• Improve docs, screenshots, and platform validation — Linux and macOS are the least tested.

For larger changes, open an issue first so the direction can be discussed.

Built with Alethe

Projects and products built with Alethe as the workspace — agents running in parallel, shells alongside them, sessions resumed across days.

Nothing here yet. Built something with Alethe? Add it to SHOWCASE.md — it's one line and a pull request, and you end up in the contributors list too.

See SHOWCASE.md for the full list and how to submit.

Watch Alethe in Action

See Alethe in real development workflows and learn how to orchestrate coding agents in parallel.

Video	What you will see
	Stop Using One AI Agent at a Time: Orchestrate AI Agents A practical introduction to coordinating multiple AI coding agents instead of working with only one at a time. Kauã Miguel - Dev · Portuguese
	A Day in the Life of a Software Developer — Devlog 1 A real-world developer workflow showing Alethe as part of the day-to-day coding process. Guilherme Dev · Portuguese

Contributors

Thanks to everyone helping shape Alethe.

License

The source code is distributed under AGPL-3.0-or-later. See LICENSE for details. Official hosted services, such as sync, backup, billing, or cloud features, may be proprietary and offered separately. The Alethe name, logo, and official branding are reserved for official builds — see TRADEMARK.md.

Community

• Security reports: SECURITY.md
• Privacy and data flows: docs/PRIVACY.md
• Maintainer: Kc1t
• Project: https://github.com/Kc1t/alethe-agents
• Bugs and feature requests: https://github.com/Kc1t/alethe-agents/issues