Skip to content
Driga

alpha · macOS, Linux · Windows experimental

See what your coding agents are doing, and what needs you.

Every Claude Code, Codex, Copilot and Gemini session across your projects and machines, live. Answer a waiting agent from the terminal or the browser.

brew install --cask labstack/tap/driga
Read the docs

A real-time screen recording of driga on demo sessions. In a terminal, driga is typed and opens; workers start under a session; that session asks permission to run pnpm prisma migrate deploy, and it is allowed with y. Then the same prompt is allowed in the browser dashboard, and a session that shares a file with another is opened. It ends on the install command.

Works withClaude CodeCodexGitHub Copilot CLIGemini CLIAntigravity (process level)

◆ NEEDS YOU

Stop checking tabs. The waiting agent comes to you.

Permission prompts, questions and finished turns land in one list, oldest first, with the full command. Allow or deny without finding the window.

How Needs you works

The web dashboard's Needs you panel: a permission prompt for pnpm prisma migrate deploy, with Allow and Deny; Allow is pressed and the wait clears.

▶ FLOW

Who is doing what, at a glance.

Sessions grouped by project, workers under the agent that started them, and a red tag when two agents edit the same file. As a map, a timeline or a plain list.

Read about Flow

The web dashboard's Flow map in light mode: sessions grouped by project, workers under the session that started them, and a selected session showing a file also touched by another session.

▣ MACHINES

Know which agent is using your machine.

Memory and CPU by session, helpers left running after an agent ends, and old worktrees you can remove, each with its evidence and a confirm step.

Projects and machines

The terminal UI's Machines tab: memory and CPU for each agent session, other apps, and machine vitals.

One collector, three ways in.

driga

Terminal UI

Keyboard first. Flow, Projects and Machines, with Chat one key away. Flow

driga web

Web dashboard

The same views in your browser, on loopback only. Light and dark follow your system. First run

driga mcp

For scripts and agents

Read-only MCP tools and versioned --json on every read command. MCP

Local by default.

No account and no API key. Driga reads session files, the process table and Git on your machine. Driga is alpha: formats and behaviour can still change.

  • Full transcripts are never stored.
  • Nothing leaves the machine unless you pair machines, over pinned mutual TLS, or use Chat and summaries, which go through your own claude CLI.
  • Open source, Apache 2.0. Privacy and data

Run it next to your agents.

brew install --cask labstack/tap/driga

Then run driga. Linux packages and Windows (experimental) are on the install page.