Glossary
Ikenga takes some of its names from the Igbo tradition. You do not need the lore to use the product: each term below leads with what it means in plain English. This page is built from the same term list the rest of the site is checked against, so it changes when the list does.
37 terms, A to Z.
- Agent saved agent persona
-
A saved agent definition (a Claude Code subagent file) that you install from Ngwa and can call on. An agent is a definition; a running one is a session, often held in a seat.
- Alusi mini-app
-
The lore name for an installed app. It appears in the first-run welcome; everywhere else copy says "app".
- App mini-app
-
An installable program with its own screen inside Ikenga, such as Studio. Apps open in a pane and install from Ngwa.
- Artifact file an agent made
-
A file an agent produces, usually HTML or Markdown, that you review in a viewer pane. You can pin comments to an artifact and compare its versions.
- Artifact grid artifact browser
-
The surface for browsing, comparing and reviewing artifacts. It has three views: a grid, a loupe for one artifact, and a compare view for two side by side. "Studio" on its own always means the Studio app.
- Bundle skill bundle
-
A set of skills that install together as one unit. The bundle lists its member skills.
- Chi agent companion
-
Your agent companion: where you hand work to Claude Code or another engine, approve what it asks to do, and watch what it costs. Chi lives in the Companion panel. Agent sessions can be held in named seats, and a session with no seat is listed as unseated.
- Command slash command
-
A single-purpose instruction you run by typing a slash, such as /init. Commands install from Ngwa.
- Companion the panel for Chi
-
The side panel for Chi. It has a dispatch bar, your seats, permission cards, a cost meter and a tool feed. It sends work to agents and shows what they ask and cost, rather than holding a conversation.
- Ekwe hook
-
The lore name for a hook. Story page and About only; copy says "hook".
- Engine agent runtime
-
The agent runtime that Ikenga drives. Claude Code is the supported engine, and the engines page lists the others with their maturity. An engine installs from Ngwa like any other extension.
- Explorer project sidebar
-
The sidebar for the active project: its files, artifacts, sessions, Ngwa items, automations, todos and scratchpads in one tree.
- Extension add-on
-
Anything you install from Ngwa that adds a capability but has no screen of its own: a tool, skill, agent, command, hook or engine.
- Hook event handler
-
A command that runs by itself when something happens, such as before a tool call. Hooks install from Ngwa.
- Ifulu agent
-
The lore name for an agent. Story page and About only; copy says "agent".
- Ikenga desktop workspace for coding agents
-
The desktop app that gives Claude Code and other coding agents a home: your projects, agents, skills and tools together in one workspace on your own machine. It is open source (Apache-2.0).
- ikenga CLI command-line app manager
-
The `ikenga` command. It lists, installs, updates and removes apps and extensions on disk, finds broken install records with `ikenga doctor`, and hot-mounts one you are building into a running app with `ikenga dev`. Write the command in code font so it is not read as the desktop app.
- iyke runtime controller
-
The command-line controller, written `iyke`, together with the local bridge inside the running app that it talks to. It lets a script or an agent navigate panes, switch modes and read live state. The bridge listens only on 127.0.0.1, behind a token made at each launch, and its routes are unstable.
- MCP pkg tool
-
The builder-docs name for a pkg that gives agents tools through the Model Context Protocol (MCP). User-facing copy says "tool".
- Member person on a shared server
-
A human who has an account on an Ikenga server, with the role Owner, Operator, Reviewer or Guest. A plan that counts people counts members, meaning Owners and Operators; Reviewers and time-boxed Guests are not counted. A member is not a seat, which is an agent slot.
- Multi-user server shared Ikenga server
-
An Ikenga server that the members of one organisation share. Members are mutually trusted; it is not built for untrusted tenants.
- Ngwa store
-
The store: one place to browse, install and manage everything Ikenga can use, which is apps, tools, skills, agents, commands, hooks and engines. It includes an Installed list, a Store and a Health page.
- Ntupo command
-
The lore name for a command. Story page and About only; copy says "command".
- Ọba store backend
-
The backend of Ngwa. It installs apps and extensions, records where each one came from and what it depends on, and takes catalogue entries from the signed Ikenga registry.
- Obi project home
-
The lore name for a project's home view. Copy uses it on the story page only; everywhere else it says "project home" or "dashboard". The shipped app still says "Obi" on first run and on the project dashboard, so a walkthrough of those screens quotes the button as it reads.
- pkg app or extension
-
The builder-docs word for one installable unit: a manifest plus whatever it contributes. Use it in builder docs only; user-facing copy says "app" or "extension".
- Project project folder
-
A folder, usually a git repository, that you have added to Ikenga. Files, artifacts, sessions, seats, todos and project-scoped Ngwa items belong to the active project, and the Explorer always shows it.
- Registry signed public catalogue
-
The public, signed index of published Ikenga apps and extensions, served from registry.ikenga.dev. Ngwa reads it, and the app refuses an index whose signature does not verify.
- Seat named agent slot
-
A named slot in a project for one agent session. You send work to the seat, and it keeps its name, its scratchpad and its address when the session behind it ends. Seats are free and are not a billing unit; the billing unit is the member. The word is unrelated to "seat of strength" in the Ikenga lore.
- Session one agent run
-
One conversation or run with an engine. A session can sit in a seat; a session with no seat is unseated.
- Signed app code-signed installer
-
The Ikenga desktop installer carrying an operating-system code signature: Apple notarisation on macOS, Authenticode on Windows. Whether a given release has one is recorded in the release facts. The .sig files on a release are updater signatures, not code signatures. Never write "signed" without saying what is signed.
- Signed pkg registry-verified pkg
-
A pkg listed in the signed Ikenga registry. The registry index carries a signature the app verifies, and each entry carries integrity hashes. A pkg can also carry its own publisher signature. This says nothing about the Ikenga installer itself; see signed app.
- Skill reusable instructions
-
A folder of instructions (a SKILL.md file) that an agent loads when it is relevant. Skills work across agent systems, and install from Ngwa or with npx skills add.
- Studio video production app
-
The Studio app: an installable app for short-form video, from script and storyboard through generation to edit. The word never names the Artifact grid.
- Trusted pkg pkg allowed elevated capabilities
-
Builder docs only. A pkg allowed to use elevated host capabilities (a host-proxied fetch, named secrets, scoped native calls). It is either built in, or published to the registry with a valid publisher signature. This is a security gate that any author can pass, not a paid tier. It is not the same as "Trusted" on the install screen, which only means you approved the pkg's permissions.
- Workspace your whole Ikenga
-
A general word for your whole Ikenga setup: the app, your projects and your personal settings. On the Store and Secrets screens "workspace" also names the personal level above projects; copy calls that level "personal".