Skip to main content
Ikenga 3 engines Download

Give Claude Code Codex Gemini CLI a home.

Your agents, skills, and running work — one desktop workspace, on your machine.

Screenshot of the Ikenga desktop workspace — a Tasks pane with an overdue launch task selected, a v0.3 launch-readiness dashboard artifact, and a terminal session, arranged in split panes.
Real capture of the shell — every feature shown ships today

Watch it work

Tasks that don't slip.

The agenda fills itself from what's due — overdue work is pulled forward, past the line marked now.

Screenshot of the Ikenga Tasks Agenda for Sunday, July 5 — an overdue 'Fix the OG card' task pulled forward, then two in-progress launch tasks, above a green now-line.
Real capture of the Tasks pkg — ships today

One click. Installed.

Ọba installs a pkg straight from the store — it resolves to an npx fetch into the vault, no restart, no config file to hand-edit.

Screenshot of the Ikenga Ọba store — a catalog of skills with 'groundwork' selected, its detail panel showing source npx, ref royalti-io/groundwork, version 0.1.0, and an Install button.
Real capture of the Ọba store — groundwork is a registry-published skill

Everything connects.

Skills, commands, MCPs, engines, and installed pkgs — one capability graph, radial-bundled the same way the shell renders it. Scroll to walk the wiring.

Ikenga capability graph Radial-bundle diagram of 17 real, shipping capabilities -- skills, commands, MCPs, engines, and installed pkgs -- grouped into 5 kind bands and joined by 23 links. Every node is keyboard-focusable via Tab; focusing one traces its links (amber outgoing, teal incoming) and opens its detail card. COMMANDS ENGINES MCPS PKGS SKILLS /release-status pkg-engine-claude-code pkg-engine-codex pkg-engine-gemini mcp-browser mcp-iyke pkg-content pkg-finance pkg-mail pkg-outbound pkg-research pkg-sales pkg-strategy pkg-tasks skill-thunderbird groundwork ikenga-artifact-builder
mcp
@ikenga/mcp-iyke
v0.2.1 · workspace
iyke control-bridge MCP server
Connections11
@ikenga/pkg-engine-claude-code gates
@ikenga/pkg-engine-codex gates
@ikenga/pkg-engine-gemini gates
@ikenga/pkg-tasks gates*
@ikenga/pkg-mail gates*
@ikenga/pkg-research gates*
@ikenga/pkg-strategy gates*
@ikenga/pkg-content gates*
@ikenga/pkg-finance gates*
@ikenga/pkg-outbound gates*
@ikenga/pkg-sales gates*
Store map 17 entries · 3 scopes
Ọba presence matrix — 17 registry entries across 3 scopes. Staged demo: presence (enabled / local / absent) illustrates the encoding.
Ọba entry ↓ / scope → royaltilaunch-weekuser
Skills 3
groundwork enabled
ikenga-artifact-builder enabled
@ikenga/skill-thunderbird local
Commands 1
/release-status enabled
MCPs 2
@ikenga/mcp-iyke enabled
@ikenga/mcp-browser enabled
Engines 3
@ikenga/pkg-engine-claude-code enabled
@ikenga/pkg-engine-codex local
@ikenga/pkg-engine-gemini local
Pkgs 8
@ikenga/pkg-tasks enabled
@ikenga/pkg-mail enabled
@ikenga/pkg-research local
@ikenga/pkg-strategy local
@ikenga/pkg-content enabled
@ikenga/pkg-finance local
@ikenga/pkg-outbound enabled
@ikenga/pkg-sales local
17 entries × 3 scopes | staged demo | presence dots illustrate the matrix encoding
Orchestration flow 1 flowable regex-derived

How this is built: the capability graph reads declarative wiring from frontmatter. This procedural sequence is parsed from the body — a lightweight regex pass, not an LLM read. Best-effort trace.

groundworkskill · 5-step pipeline
1
research — sweep sources; stamp the 02/03 research docs
2
design — draft boards + interactive prototypes
ikenga-artifact-builderskill
3
plan — cut the spine into cuttable work packages
4
orchestrate — fan work packages out to subagents
5
act — augment the plan docs in place, no clobber
Beat 1 · Radial graph

One capability graph.

Skills, commands, MCPs, engines, and installed pkgs — radial-bundled exactly the way the shell's Ngwa analyzer renders them.

Staged demo — every node is a real, shipping capability.

Beat 2 · Select a node

Click one, read the wiring.

The info board is the shell's own detail card — kind chip, scope, description, then every connection with its relation verb. * marks a heuristic (inferred) edge.

outgoing · incoming · dashed = heuristic

Beat 3 · Store map

The breadth, at a glance.

Every store-backed primitive × the scopes it lives in. One matrix shows how far the workspace reaches — enabled, local, or absent per scope.

Presence matrix — the shell's Ọba store map.

Beat 4 · Flow view

How the work moves.

Declarative wiring is only half the story. The flow view traces the procedural step-sequence inside a skill — numbered steps and the capabilities each one calls.

Orchestration flow — parsed, best-effort.

Staged demo — every node, store row and flow step is a real, shipping capability · hover or tab through a node to trace its links and open its card

Everything is a package.

Mini-apps, tool servers, engine adapters — every capability docks into your workspace as an independently installable package. Claude Code is the default engine; Gemini CLI and Codex install the same way. Add what you need, retire what you don't.

@ikenga/pkg-tasks v0.8.3

Tasks — List, Agenda, Triage over the production tasks schema.

@ikenga/pkg-mail v0.3.0

Mail — Inbox, Triage, All, Drafts over the production mail schema.

@ikenga/pkg-research v0.2.0

Research — Reports, Sources, Personas over the research_notes + research_sources schema.

@ikenga/pkg-strategy v0.2.0

Strategy — OKR board (board + list), Cycles, Reviews over the production strategy schema.

@ikenga/pkg-content v0.3.0

Content — Pipeline, Calendar, Published over the production content schema.

@ikenga/pkg-finance v0.3.0

Finance — Overview, Transactions, Receivables, Inter-Company, Reports over the production finance schema.

@ikenga/pkg-outbound v0.3.0

Outbound — Email, Newsletter, Sequences, Social channels over the production outbound schema.

@ikenga/pkg-sales v0.3.0

Sales — Pipeline, Forecast, Won over the production sales schema.

Browse all packages →

Install

The skills work anywhere.

Skills, agents, and commands are plain files — that's why they're portable across systems. groundwork and artifact-builder run in Claude Code today, no shell required; Ikenga is Claude-first, with Gemini CLI and Codex supported too. Ikenga is where these primitives get a visual home: boards in panes, artifacts you can see, a workspace that remembers.

Install the workspace

macOS · Linux · Windows, one line.

curl -fsSL https://ikenga.dev/install.sh | sh

Auto-detects your platform. On Linux it pulls the ~17 MB .deb when dpkg is present (or a ~101 MB AppImage, no sudo); on Windows, winget install Ikenga.Shell also works.

Add a skill to Claude Code

Works today, with or without the app.

npx skills add royalti-io/groundwork

Or skip the app. Add a skill to plain Claude Code anywhere — groundwork and ikenga-artifact-builder work with or without Ikenga. More skills are coming.

  • Apache-2.0
  • Local-first
  • No account required
  • Claude-first · Gemini & Codex too

Welcome to your Obi.

We didn't build Ikenga to sell it. We ran our own company on it for eighteen months first — the same shell, skills, and agents you're about to download, doing real day-to-day work. That's the proof it works, not a feature you have to take on faith.

We built it to run our own company. Now it's yours.

  • Your config lives on your machine — readable as files, versioned in git.
  • Every agent, skill, and command you install is yours to inspect and change.
  • The cockpit keeps you in sync across projects — no dotfile archaeology.

Apache-2.0. No account required. Read every line.

Obi — the meeting house; the home of your workspace.