Clauge

You've been flipping between multiple apps to do one job. Clauge runs all of them in one shell — coding agents, an API client, SQL and NoSQL editors, SSH sessions, a remote file browser, and a project workspace — and gives each mode its own AI, tuned for that workflow. Every mode is one keystroke away. Your data stays on your machine.

Modes

Plus a cross-mode History layer — a queryable log of every session, request, query, and command across modes.

Inside each mode

Agent

Spawn coding agents in parallel — Claude, Codex, Gemini, OpenCode — without ever leaving the editor. Each session is independent: its own git worktree, its own context, its own model.

Per-session controls:

• Purpose — pin the session's intent up front (see table below)
• Git identity — commit as a coworker, not yourself
• Skip permissions — for fully-autonomous runs when you trust the prompt
• Context injection — pin files, folders, or MCP servers via the Context Manager (save sets, reuse across sessions)
• Plugins — load extra tools from the Plugin Manager

Purposes

Every Clauge session has a purpose that shapes the agent's focus from the first message. No more prompting it to "act like a code reviewer" mid-conversation.

Every session emits usage analytics — tokens in / out, cost, cache hit, model mix — per session and aggregated across your day.

Workspace

A shared layer your agents can read, write, and act on through MCP.

• Kanban boards — Backlog → Todo → In Progress → In Review → Done. Review is a safety gate, not a column you skip past.
• Two-way Git integration — pull open issues from GitHub and GitLab into a board, push finished cards back as pull requests.
• Project linking — point a workspace at a git repo and Clauge auto-spawns one board per subproject.
• Notion-style notes — a real WYSIWYG markdown editor, not a textarea. Per-project, linked to sessions, exposed through MCP.
• AI coworkers — named personas (Tech Lead, Brainstormer, Developer, Reviewer, QA) with their own prompts and providers. They read cards, comment, request changes, claim work, commit, and raise PRs.
• Single-owner lock — only one coworker (or one terminal session) owns a card at any moment. Switching owners, claiming from a terminal, and chatting in the card drawer all go through the same lock — no race conditions, no lost work.
• Pinned Inbox — mentions, review requests, and approval queues across every board, in one pane.
• Cross-board search — instant full-text search across every note and card.
• Default-on MCP — boards, cards, notes, and @-mention a coworker are all MCP tools an external agent can call. Auto-starts when the app launches — no flag, no setup.

REST

An API client driven by AI and exposed over MCP.

• MCP integration — external agents can list, read, create, update, and delete collections and requests.
• AI assistance — describe an endpoint and the AI writes the request; ask "run the smoke tests in staging" and the AI fires the whole collection.
• Execution reports — pass / fail summary with the failing request inline.
• Collections, environments, request history, Postman v2 / v2.1 import.

SQL

One editor, multiple engines, schema-aware AI.

• Engines — PostgreSQL · MySQL · ClickHouse · SQLite · Cloudflare D1
• AI assistance — natural language → schema-aware SQL, ready to run
• Cross-dialect translation — Postgres → MySQL → ClickHouse; AI rewrites the query for the target engine
• SSH tunneling shared with other modes — wire your bastion once, all modes use it

NoSQL

Document stores and key-value engines, side by side.

• MongoDB — collections, JSON query editor, stage-by-stage aggregation pipeline builder with previews
• Redis — keys, TTL, streams, pub-sub, interactive console
• Engine-aware AI — never confuses a find with a SCAN

SSH

Persistent SSH with two AI modes:

• Permission mode — every command the AI proposes is gated; you approve before it touches the wire.
• Auto mode — describe what you need; the AI executes and streams the output back.

Plus: reusable profiles, multiple tabs against the same host (no re-authenticating), port forwarding, ed25519 and agent forwarding, keychain-backed credentials.

Explorer

Every backend, one browser, one set of shortcuts.

• Backends — Local FS · Amazon S3 (and S3-compatibles like R2, MinIO, Wasabi) · Azure Blob · SFTP · FTP
• One-click presets — pre-configured profiles for the common S3-compatible providers, so connecting takes seconds
• Drag-and-drop transfers — drop files into any backend, right-click "Download to…", with a live transfer panel showing progress and cancel
• AI assistance — "what grew today?", "find images larger than 5 MB" — natural-language file ops
• Inline preview — text, JSON, CSV without a round-trip download

Atlas

A free-form spatial workspace where every open tab becomes a draggable window. Pan, zoom, snap to neighbors, and stop alt-tabbing.

• Universal tile — Agent sessions, SSH terminals, REST requests, SQL editors, NoSQL queries, Explorer file browsers, and Atlas-spawned shells all coexist as resizable windows on one canvas.
• State preserved across modes — switching to Atlas and back doesn't reset anything; CodeMirror undo stacks, scroll positions, terminal scrollback, and connection state survive the round-trip.
• In-tile control surfaces — SQL tiles get a Run button + results table + connection picker; NoSQL tiles get a connection/collection picker; REST tiles get the full headers/auth/params/body editor + env picker + Send.
• Snap guides + per-workspace layouts — tiles snap to the edges of neighbors while dragging; tile positions are persisted per workspace, so each project has its own canvas memory.
• Spawn shells anywhere — a shell-spawn button drops a fresh terminal onto the canvas, scoped to that work