npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

agent-takkub

v1.0.25

Published

Desktop cockpit for orchestrating a team of Claude Code agents (Windows + macOS)

Downloads

6,625

Readme

🛩️ agent-takkub

Your AI dev team — in one desktop cockpit.

Prompt one Lead agent. It plans the work, splits it across specialist teammates, runs them in parallel as real claude processes, and verifies the result — while you watch and steer.

NPM Version Downloads License Platform

npm install -g agent-takkub

100% local · runs on your logged-in Claude Code CLI · no SaaS middleware


🖥️ The Desktop Cockpit

Takkub Cockpit — Lead + specialist teammates working in parallel


✨ Why agent-takkub?

A single AI agent hits a wall on big work: context fills up, sub-tasks collide, and everything runs one-at-a-time. agent-takkub runs it like a real engineering team — a Lead you talk to, and specialist teammates it delegates to, each in its own isolated claude process, working concurrently.

| | | | :-- | :-- | | 🧠 Orchestrated teammates | Converse with the Lead; it spawns, tasks, and manages specialist panes (frontend, backend, qa, reviewer, devops, mobile, …) on demand — only the roles a job actually needs. | | 🔀 True parallelism | frontend and backend build a feature at the same time; QA always verifies last, against the real running stack. | | 🌿 Branch & worktree isolation | Parallel teammates each work on their own git branch in an isolated worktree — no commit races, no dirty-state collisions. You merge when ready. | | 👥 Fleet mode | One toggle scales a role into a fleet (frontend#1…#K) sized to your machine — for many independent features or sharded test suites at once. | | 🖥️ Steerable, always | Every pane is a live claude shell. Watch output in real time, interrupt, or type straight into any teammate. | | 🗂️ Multi-project tabs | One isolated Lead per project — no cross-talk. | | 🔒 100% local | No SaaS middleware. Everything runs on your machine, on your logged-in Claude Code CLI. |


🧠 One team, three model "brains"

Model diversity beats a single point of view. Takkub lets the Lead pull in a second and third brain for planning, review, and cross-checks — and it never breaks if you don't have them installed.

| Brain | Backed by | Great at | | :-- | :-- | :-- | | 🟣 Claude | Claude Code CLI | The Lead + every specialist — build, test, review | | 🟢 Codex | OpenAI Codex CLI | Second opinion · refactor patterns · cross-checking a plan | | 🔵 Gemini | Google Antigravity (agy) | Long-context planning (reads the whole repo) · a third perspective |

Never a hard dependency. If Codex or Gemini isn't installed (or you've toggled it off), the Lead keeps the role — Claude transparently stands in, and tells you you've traded away model diversity. No refusals, no dead ends.


⚡ Quick Start

# 1. Install the cockpit globally  (isolated Python runtime + a Desktop icon)
npm install -g agent-takkub

# 2. Authenticate with your Claude account (if you haven't already)
claude login

# 3. Provision recommended plugins + browser-automation tools (idempotent)
takkub provision

⚠️ Install it globally — the -g flag matters. It provisions the isolated runtime and the Desktop launcher. A plain npm install agent-takkub (no -g) will not set the app up.

Then double-click “Takkub Cockpit” on your Desktop — or launch from a terminal:

agent-takkub

Requirements — Node.js ≥ 18 and Python ≥ 3.11 already on your system. They're detected, never reinstalled. Everything else lives in an isolated ~/.agent-takkub; your existing claude CLI, plugins, and config are left completely untouched.


🚦 Two ways to run: 1:1 or a whole team

A chip in the status bar flips how the Lead works:

  • 👤 1:1 (default) — one agent per role, one feature at a time. Focused and predictable.
  • 👥 Multi — hand the Lead several independent features and it fans out into multiple instances per role (frontend#1…#K, backend#1…#K) running at once, like a team of several devs per position. Finishes fast.

Dependent work stays sequential automatically; QA is always the final gate, run against the real stack.


🔄 Orchestration Flow

sequenceDiagram
    actor User
    participant Lead as Lead Agent
    participant Cockpit as Cockpit Engine
    participant Spec as Specialist Pane(s)
    participant Git as Git Repository

    User->>Lead: "Build the login feature"
    Lead->>Cockpit: takkub assign --role frontend / backend (parallel)
    Cockpit->>Git: create isolated branch + worktree (optional)
    Cockpit->>Spec: spawn claude pane + inject task
    Note over Spec: teammates code & test independently
    Spec->>Cockpit: takkub done "report"
    Cockpit->>Lead: done notice → verify sequence (devops → QA last)
    Lead->>Git: review + merge branches, propose ship

📱 Mobile Remote Control (PWA)

  • 📲 Install-free PWA — open the paired link, Add to Home Screen, done. Offline-capable app shell, no store.
  • 💬 Live Lead console — the Lead's replies stream to your phone in real time (with a "still working…" indicator); type back to steer it.
  • 📊 Pulse — a glanceable, project-grouped view of which teammates are running and for how long.
  • 🎛️ View vs. control — read-only by default; flip to control mode to send prompts or open projects remotely.
  • 🔒 Three-factor, off by default — secret path + bearer token (never in the QR) + a password gate, on a loopback-only server behind a Cloudflare/ngrok tunnel, with per-client sessions & brute-force lockout. Data-minimized: never ships raw tool output, commands, or filesystem paths. Turn it on from the cockpit's 🌐 Remote chip.

🛠️ Everyday Commands

| Command | Purpose | | :--- | :--- | | takkub assign --role backend "…" | Spawn a specialist and assign a task | | takkub assign --role frontend --isolation worktree "…" | Task on an isolated git branch + worktree | | takkub assign --role qa --plan --shards 4 "…" | Plan-first parallel browser QA (auto fan-out) | | takkub worktree list / merge / clean | Review + merge isolated branches | | takkub send --to qa "…" | Message a teammate (Lead CC’d) | | takkub goal "…" | Set a session goal injected into every task | | takkub restart | Restart the whole cockpit from the terminal | | takkub doctor --fix | Diagnose the environment + auto-repair | | takkub provision | Install / repair plugins + browser tools |


📖 Deep Dives & Resources