Open source desktop app

Drag a card.
An agent starts.

An agentic development environment for AI coding agents. Spawn, suspend, and resume sessions across fifteen agent CLIs from one board, with your own backlog and your own workflow. Local, free, open source.

The desktop app
npx kangentic
The mobile companion

This is Kangentic, replaying recorded agent sessions on a sample install.

Open the demo

Esc also returns

The steps

How it works

Four steps from a board you define to a diff you can merge.

  1. Configure your board

    Shape the board around your workflow: the columns a task moves through, and the agent and permission mode each one runs. Keep the default board or make it your own.

  2. Create a task

    Add a card with a title and prompt, plus screenshots, a source branch, and worktree isolation. Or let an agent file it through the built-in MCP server.

  3. Drag to run

    Drag the card to an active column. Based on your board configuration, Kangentic creates a worktree, applies the permission mode, and starts the agent.

  4. Watch it code

    The agent starts writing. Follow along in its live terminal: diffs, test results, and tool calls as they happen.

The problem

The problem with parallel agents

01

Agents finish real work now

A coding agent can take a task from prompt to a diff on its own. Give each task its own git worktree and you can run a dozen of them at once, across every project you own, and ship faster than one person can keep up with.

02

The bottleneck moves to you

Which one is waiting for an approval? Which one just finished? Which branch conflicts with which? A dozen terminals across three projects turns your day into a search for the one that needs you, and that is exactly where the speed goes.

03

One board, every agent

Kangentic drives the agent CLIs you already have and puts every session on one board, in columns you define. Each card shows its model, how much of the context window is used, and what the agent last said, with a mark on the ones that need you. Answer those from the board or from your phone, and let the rest work.

Agents

Any Agent, One Board

Fifteen agent CLIs on one board. Spawn, suspend, and resume sessions with a drag.

Run Claude Code, Codex, Gemini, Cursor CLI, GitHub Copilot CLI, Grok Build, Antigravity, Goose, OpenCode, Aider, Qwen Code, Kimi Code, Factory Droid, Warp (Oz CLI), and Ollama side-by-side on the same Kanban board. Drag tasks to spawn, suspend, and resume sessions. Mix agents per column and hand off context between them.

Claude Code Codex CLI Gemini CLI Cursor CLI GitHub Copilot CLI Grok Build Antigravity CLI Goose CLI OpenCode Aider Qwen Code Kimi Code Factory Droid Warp (Oz CLI) Ollama

Docs Agent orchestration Activity detection Session persistence

Backlog

Bring your own backlog

Import issues, project cards, and work items from the tools your team already uses.

Board Backlog 5 Import
Rotate the staging API keys 2 hours ago
Add UI scale setting to Appearance 1 day ago
Fix login redirect loop just now
Search ignores hyphenated names just now
Upgrade Webpack to v6 just now

Pull tasks in from GitHub Issues, GitHub Projects, Azure DevOps, and Asana, including titles, descriptions, labels, and inline images. Triage them in the backlog, then batch-promote to any column when you're ready to run agents. Already-imported items are detected automatically so re-syncing is safe.

GitHub Issues GitHub Projects Azure DevOps Asana Jira Soon Linear Soon Trello Soon GitLab Soon Obsidian Soon

Docs Backlog Importing issues Creating tasks

Workflow

Bring your own workflow

Workflows run linked tasks in order, columns run their own rules, and agents drive the board through MCP tools. Use one, or mix all three to fit how your team ships.

Customize / Workflows
The Workflows view on Harden the API, a running workflow of six linked cards: two done, two in progress, and two waiting in To Do. Green links run from the done cards and grey links into the waiting ones, beside the run order.

Docs Workflows Automations MCP tools

  1. Turn ends The agent finishes a turn The task is still in its column, and its agent waits.
  2. Automations The column's automations run first Top to bottom. If one moves the task, say back a column, that move wins.
  3. Workflows Then the workflow moves it on Once its check finds the work done, even with no automations set up.
  4. Next column The task enters its next column Its automations run there, and the cycle starts again.

Features

Everything on one board

Pick a feature to see it in the app, or let the tour play.

  1. Your CLIs, your machine

    Kangentic runs on your desktop and launches the agent CLIs you already have, with your own logins and subscriptions.

    • Finds each installed CLI and flags any that need a sign-in
    • Boards, tasks, and transcripts stay in a local database
    • Analytics never include your code or task content
    The welcome screen with its setup list open: a prompt to sign in to OpenCode, OpenCode on top marked Not signed in with its login command to copy, git and three agents found with versions, and three more marked Not installed beside an Install link.
  2. Column Manager

    Every project gets its own board. In the Column Manager you add and reorder columns, then decide what each one does.

    • Start an agent in a column, and pick which one
    • Set permissions per column, from what that agent supports
    • Share the task's conversation, or start clean on every entry
    The Column Manager dialog with the Code Review column selected: its name, icon, and color, Codex CLI on gpt-5.5 as the agent that starts when a task enters it, and empty automation slots for entering and leaving the column.
  3. Model & effort routing

    Give each column its own agent, model, and effort, and save the whole ladder as a board profile. Cards pick up the change as they move, so you never type a /model command.

    • Plan on a heavy model, merge on a lighter one
    • Pin one task to its own agent and model with Agent Override
    • Profiles live in kangentic.json, so your team shares them
    The Column Manager's All columns table: Claude Code plans on Opus 5 at xhigh and builds on Sonnet 5, Codex CLI reviews on gpt-5.5 in an isolated session, and GitHub Copilot CLI merges, with handoff on at each change of agent.
  4. Git worktrees

    Each task runs in its own worktree on a new branch from your base branch, so parallel agents never collide and your project folder stays untouched.

    • Name the branch, pick the base, or run in the project folder
    • Update from base fast-forwards only, never merges or rebases
    • Done keeps the branch; drag the card back to pick up again
    Settings on the Git tab in three cards: Branches with the default base branch and auto-fetch, Worktrees with its switch, cleanup, node_modules linking, and files and a script for each new worktree, and Pull requests with auto-refresh and merge bypass.
  5. Status on every card

    Every card shows whether its agent is thinking, idle, or waiting on you, read from each CLI's own hooks where it has them.

    • The agent's latest message, right on the card
    • Per-project counts in the sidebar
    • A desktop alert or a phone push when one needs you
    The Kangentic board for contoso-web: columns from To Do to Testing, each card showing its agent, latest message, and context use, three projects in the sidebar, and the terminal panel along the bottom on the working auth-middleware agent.
  6. Built-in MCP Server

    Most agents get Kangentic's MCP tools in every session, with nothing to install. They file and move tasks, search past sessions, message another task's agent, and drive the Browser pane.

    • Runs inside the app on localhost, with a fresh token each launch
    • Added per session, so your own MCP servers keep working
    • Reserves free dev ports so parallel agents never clash
    Settings on the MCP Server tab: one card with the server switch and, inside it, a Documentation row and the available tools in collapsible groups by area: tasks, board, sessions, and more.
  7. Agent Browser

    Agents drive a real browser beside their terminal: they open your dev server, click through what they built, read the console and network, and screenshot the result.

    • Draw on the page or inspect an element, then send it as a prompt
    • Each agent can reach only its own project's Browser panes
    • Switch clicks, navigation, and eval on or off in Agent Browser settings
    A task window with the Browser pane open beside the agent's terminal: an address bar on the project's local dev server, the page it serves loaded beneath, zoom and Close browser controls above, and Draw, Inspect, and a note field for the agent below.
  8. Agent Monitor

    One overlay lists every live agent session across every project, as cards, a table, or a list, with a peek at each session's latest output.

    • Group by project or status, and filter by agent, model, or label
    • Open any task right inside the monitor
    • Pop it out onto a second display
    The Agent Monitor over all three projects: summary tiles for idle, active, and paused sessions, then a card per session grouped by project, each with its column, its latest output, and its model and context use.
  9. Changes panel

    Review an agent's work without leaving Kangentic: a file tree, a split or inline diff, and the branch's commit history.

    • Switch between working, staged, and whole-branch changes
    • Tick files off as viewed, and the marks are kept
    • Blame, Markdown preview, and keyboard jumps between changes
    A maximized task window with the Changes panel open on the Branch tab, which compares the task branch against main: the file tree lists server/routes.ts and middleware/auth.ts with their line counts, and routes.ts is open in the diff pane.
  10. Knowledge Graph

    Turn it on and your past conversations, tasks, and commits become a map you can explore and search by meaning. Ask a question and an agent you pick answers from it.

    • Indexes conversations, tasks, commits, and source code
    • The index, the map, and the search run on your machine
    • The answering agent can search, never change anything
    The Knowledge Graph across three projects: contoso-web, spring-petclinic and online-boutique as islands of conversation points joined by links, regions named over them, the Filter, Regions and Display cards on the left, and an Ask box above.
  • Tasks

    Create tasks

    The title and description become the agent's first prompt. Add files, a priority, and labels, or let an agent file the task for you through MCP.

    • Paste or drop any file; large screenshots are compressed for you
    • Type @ to autocomplete a file path in the description
    • Follow the column settings, or pin one agent for the whole run
    The New Task dialog: a title field, a description editor that takes dropped files, priority and labels, the Branch row with the branch it will create from main in a new worktree, and the choice between the column's settings and an agent override.
  • Backlog

    Backlog, labels & priorities

    Stage work in a backlog before it reaches the board, then promote a batch to any column in one move.

    • Rename and recolor labels, and shape your own priority scale
    • Filter and search the same way on the backlog and the board
    • Import from GitHub Issues, GitHub Projects, Azure DevOps, or Asana
    The Backlog view: a table of unscheduled items with a priority badge, title, description, labels, and age for each, under a toolbar with search, filter, New Task, and Import Tasks.
  • Handoff

    Handoff context

    Switch on handoff for a column, and when a card arrives from a different agent, the new agent reads the previous one's conversation instead of starting from the task title.

    • Passes the real history file, not a summary
    • Any agent can receive a handoff
    • With no history to pass, the next agent gets the git log
    The Column Manager's All columns table: Claude Code plans on Opus 5 at xhigh and builds on Sonnet 5, Codex CLI reviews on gpt-5.5 in an isolated session, and GitHub Copilot CLI merges, with handoff on at each change of agent.
  • Activity

    Activity tab

    The Activity tab in the bottom panel turns raw terminal output into one readable feed for the project's sessions.

    • Each tool call, and the file it touched
    • When an agent went idle or is waiting on you
    • Sessions spawning, suspending, and resuming
    The terminal panel on its Activity tab: a timeline of tool calls across every running session, each line stamped with its time, its session, and the tool, with a filter above it.
  • Context

    Context bar

    A live strip under every terminal shows the model, cost, tokens, tool calls, elapsed time, and, where the agent reports it, how full the context window is.

    • Click the model or effort pill to change it for that task
    • Click tool calls for a per-tool breakdown
    • Turn each stat on or off in Task settings
    Settings on the Task tab: card density, card preview, ticket numbers, and a switch for each pill the context bar shows.
  • Merge

    Pull requests

    When an agent opens a pull request, Kangentic links it to the task and keeps its status on the card.

    • Works with GitHub and Azure DevOps, or paste a PR in by hand
    • The badge says ready, blocked, conflicts, or checks running
    • Rechecks open PRs on its own, faster while checks run
    The Kangentic board for contoso-web: columns from To Do to Testing, each card showing its agent, latest message, and context use, three projects in the sidebar, and the terminal panel along the bottom on the working auth-middleware agent.
  • Sessions

    Session persistence

    Every session is written to a local database as the agent works, so a crash, a restart, or a pause never loses it.

    • Agents resume their own conversation where the CLI supports it
    • Sessions you paused stay paused after a relaunch
    • Terminal scrollback comes back with them
    The contoso-web board in Planning: the Fix WebSocket reconnection card shows its agent's last message and reads Resuming agent..., the Onboarding empty states card below it reads Paused, and the agents in Executing are working.
  • Usage

    Usage Stats

    One dashboard for what your agents cost and consume: tokens, cost, sessions, tool calls, and burn rate, for one project or all of them.

    • Live, today, this week, this month, or all time
    • Break it down by model, agent, and reasoning effort
    • Totals survive deleting tasks and sessions
    The Usage dashboard for all projects this week: token, cost and burn rate tiles, session and tool counts, a Background card for the calls Kangentic makes itself, cost per day by model beside cumulative spend, and breakdowns by agent, model and effort.
  • Search

    Quick Find

    One shortcut, from anywhere, searches tasks, the backlog, session events, and every past agent conversation by keyword.

    • Type #42 to jump straight to a task
    • Opens a past conversation at the exact turn that matched
    • Hand any search to the Knowledge Graph from the last row
    The Quick Find palette with "auth" typed into it, and grouped results beneath: the tasks whose titles or descriptions match, and the session events where an agent touched an auth file, each with the match highlighted.
  • Windows

    Docking windows

    Open several task windows at once and tile them side by side to watch agents work, or pop a panel out onto a second monitor.

    • Snap to a half, a corner, or full size, by pointer or keyboard
    • Drag a window onto another to tile them, then drag the seam
    • Layouts come back per project after a restart
    Two task windows tiled side by side over the board, Extract auth middleware on the left and Generate API client types on the right, each with Claude Code working in its terminal and a context bar below it showing the model, context use, and cost.
  • Command

    Command Terminal

    One shortcut opens a quick agent session at the project root, with no task card. It fetches and fast-forwards your base branch first.

    • Run several at once, tiled side by side
    • Switch model or effort on the fly from its context bar
    • Keeps running when you hide it or switch projects
    Two Command Terminal windows tiled side by side: on the left Claude Code has summarized the repository and listed its npm scripts in a table, on the right a second Claude Code has just started in the same project root and waits at its prompt.
  • Voice

    Voice dictation

    Hold your push-to-talk button and talk into any input in the app: a task description, a message to an agent, a settings search. It is free and needs no API key.

    • Runs on your machine by default; a cloud final pass is optional
    • A live preview as you talk; Best adds a more accurate pass on release
    • Bind it to a key chord or a mouse side button
    The Settings panel on the Dictation tab with its search box focused and the dictation chip under it: a live dot beside Listening, a hint that releasing the key sends the words, and a Clear control, over dictation settings in Best mode.

Mobile

Check on your agents from your phone

Pair a phone to your desktop once. Read what an agent is doing, answer the question it stopped on, and review the diff before it lands.

  • Encrypted end to end
  • Self-hostable relay
  • No account
Mobile / Agents
The Agents tab in Kangentic Mobile, with a session waiting on approval at the top of the Idle group

Docs Install Pairing a phone Security

FAQ

Frequently Asked Questions

Which AI coding agents does Kangentic work with?

Fifteen agent CLIs:

  • Claude Code (Anthropic)
  • Codex CLI (OpenAI)
  • Gemini CLI (Google)
  • Cursor CLI
  • GitHub Copilot CLI
  • Grok Build (xAI)
  • Antigravity CLI (Google)
  • Goose CLI (Block)
  • OpenCode (sst)
  • Aider
  • Qwen Code (Alibaba)
  • Kimi Code (Moonshot AI)
  • Factory Droid
  • Warp (Oz CLI)
  • Ollama (local models, single-turn chat)

Drag a task to any active column and Kangentic spawns the configured agent's CLI in an isolated git worktree, streaming the terminal into the app. Set a default agent per project and override it per column, so a task can hand off from Claude in Planning to Codex in Executing without leaving the board.

Won't parallel agents conflict with each other in my repo?

No. Each task runs in its own git worktree on its own branch, so agents work in separate checkouts and never see each other's half-finished changes. Your main working directory is never touched. Review each task's diff in the built-in Changes panel and merge on your own terms, or flip a single task to run in the project folder itself when isolation would only get in the way.

Do I need an API key or cloud account to use Kangentic?

No. Kangentic runs the agent CLIs you already have, with the credentials you already configured: no OAuth, no API proxy, no Kangentic account. Your boards, tasks, and transcripts stay in a local SQLite database. The app itself sends only anonymous analytics and crash reports, which KANGENTIC_TELEMETRY turns off, plus update and announcement checks; the CLIs you run still reach their own providers under your own accounts. Full details in the Privacy Policy.

Is Kangentic free and open source?

Yes. Kangentic is free forever under the AGPL-3.0 license, with every feature included and no paid tiers. The source is at github.com/Kangentic/kangentic.

What operating systems does Kangentic support?

Kangentic is a cross-platform Electron desktop app with native installers for Windows (NSIS, x64), macOS (DMG, Apple Silicon and Intel), and Linux (deb and rpm, x64 and arm64). WSL users should install the Windows version.

Is Kangentic just a Kanban board for AI coding agents?

No. The board is the interface; what runs underneath is an agentic development environment (ADE). Dragging a card spawns, suspends, or resumes an agent CLI in its own git worktree, with live terminals, diff review, linked PRs, and an embedded browser to preview what agents build. The columns are automation you define: each carries its own agent, model, permissions, and a message to send the agent, a script, a webhook, or a notification when a card arrives or leaves. Backlog import brings work in from the tools your team already uses, handoff carries context between agents mid-task, and the board's own MCP tools let agents create tasks, move cards, and message other running sessions.

How is Kangentic different from running agents in separate terminals?

Running agents in separate terminal tabs scales poorly: you context-switch between windows, lose track of what each one is doing, and have no shared view of progress. Kangentic drives the same CLIs under the same accounts, but puts every session on one board: column moves start, suspend, and resume agents, each task gets its own git worktree, and a unified activity view shows which agents are thinking, idle, or waiting for approval. The workflow those columns run is the one you define, not one Kangentic imposes.

More frequently asked questions

Built with

Built with

Modern, battle-tested technologies for reliability and performance.

Electron xterm.js SQLite React TypeScript Tailwind Vite Playwright

Dogfooding

Kangentic builds Kangentic

Every feature of Kangentic was planned, built, and reviewed by agents on a Kangentic board: the desktop app, this website and its docs, the mobile companion, the relay. Here's a slice, mid-flight:

To Do 2
kangentic
Rebrand the desktop app icons to v2
kangentic-mobile
Blind pairing QR flow
Planning 1
kangentic-branding
Add blink and wave mascot frames
mascot
GPT-5.6 Sol24%
Executing 1
kangentic.com
Redesign in the Warm Craft design language#46
designredesignlanding-page
Fable 557%

Yes, really. The card in Executing is this very page.

Ready to put your agents on one board?

Under a minute with the CLIs you already have. Free and open source.