omp packages

@ignitionai/cogitator0.5.0

A web control panel for pi: composable agents, workspaces, interactive conversations, and scheduled tasks. A pi package.

salim4n Published 2 days ago MIT ~789 downloads/mo

Untested on omp

This is a pi package. No one has reported whether it works on omp yet. If you try it, add your result below.

Did it work for you?

Result

One report per person. A new report replaces your old one.

Reports 0

No reports yet.

Readme

Cogitator — nebula gear logo

Cogitator

A web control panel for pi — composable agents, workspaces, GitHub-native kanban, and scheduled tasks.

GitHub npm version pi package license

Cogitator lets you orchestrate pi processes from your browser: compose agents from a provider, model, thinking level, skills, MCP servers, and subagents; manage project workspaces; and dispatch work through a kanban board backed by GitHub Issues. Track the work through modified files, diffs, and a chronological activity feed.

The entire application interface is available in English and French. Use the Language / Langue selector in the sidebar (inside the menu on mobile). The first visit follows the browser’s supported language preference, falling back to English; your choice is remembered locally and updates open screens without losing drafts. Dates and numbers follow the selected language, without changing the scheduling timezone.

User content, agent responses, editable agent presets, code, files, and technical identifiers are preserved as authored. Cogitator’s controls and diagnostic explanations are translated; external diagnostic details remain available in their original form. The documentation is in English.

Install the pi extension

Cogitator ships as a pi package. pi install does not start the app. It only registers an extension: a /cogitator slash command, loaded the next time you open pi. The extension itself stays idle until you run that command (it must not spawn a server just because pi started).

You need pi and Node.js ≥ 22.19.0.

pi install npm:@ignitionai/cogitator

Confirm with pi list. Then, inside a pi session, type:

/cogitator

What that does:

  1. Looks for a Cogitator server already answering on http://127.0.0.1:5320.
  2. If none is up, starts cogitator in the background (detached). Closing pi does not stop it — scheduled tasks keep running.
  3. Opens the control panel in your default browser.
  4. Prints the URL in pi. Default: http://127.0.0.1:5320.

State lives in ~/.cogitator (SQLite catalog). Conversation transcripts stay in pi’s own JSONL files. Later: pi update --extensions to refresh, pi remove npm:@ignitionai/cogitator to uninstall the package (this does not delete ~/.cogitator).

If pi reports Cogitator unavailable: something else is bound to port 5320, or an older/incompatible Cogitator is still running. Stop that process and run /cogitator again. Auth-required instances also refuse a plain loopback probe until owner login is in place.

Run the server yourself

Same process, foreground, no pi session:

npx @ignitionai/cogitator

Logs the URL, then waits. Ctrl+C stops it. After a global npm install you can also run cogitator. Optional flags: cogitator --auth-required, and cogitator auth init|recover|setup-key for single-owner login. Override bind with COGITATOR_PORT / COGITATOR_URL if 5320 is taken.

Local loopback only

The default app is a trusted service on 127.0.0.1, not a secured remote product. Do not put it behind a public proxy.

Native single-owner login and MFA has passed independent code re-reviews and bounded local verification (Node 22/26, real local HTTPS/browser journeys). Login is not isolation of agent execution. Public remote operation, autonomous recovery, and the remaining Durable work are not approved. See the evidence and remaining gates.

Features

  • Composable agents — each preset combines a provider, model, thinking level, explicit skill set, MCP servers, scope prompt, and subagents. These become native pi flags when the process starts (--model id:thinking, --no-skills --skill …, --append-system-prompt).
  • Three built-in agents — Majordome (the default operator), Chef de Projet (project management, board dispatch, and the to-tickets/use-delegate methods), and Architecte de Skills (SKILL.md authoring). Includes their skills and the Cogitator MCP server with 28 tools.
  • Project workspaces — a dedicated page for each directory, with a board, file activity (+/−), chronological feed, read-only file tree, team overview, project manager chat, and one-click project setup.
  • GitHub-native kanban — each card is a GitHub issue, with status:/priority: labels, native blocking relationships, and writes through gh. No synchronization layer: GitHub remains the single source of truth.
  • Agent dispatch — use “Lancer l’agent” (launch agent) on a ticket to start a conversation in its workspace, link the card to its activity, and move it to in progress.
  • Conversations — SSE streaming with reconnection recovery, copyable code, structured tool output and diffs, pasted images, history, and skills invoked with /skill:name.
  • Live model settings — change provider, model and reasoning in a classic chat or for an individual group member, without losing history. Changes wait for the current response to finish. Apply to the conversation only, or explicitly also save the bot's defaults for future conversations; existing sibling chats stay unchanged. Durable missions keep their frozen configuration. A pending change interrupted by a controller restart requires an explicit retry.
  • Automatic interactive UI — agents choose between text, forms, choices, checklists, and tables as needed, in both standalone and workspace conversations. Responses are submitted explicitly and saved in pi JSONL transcripts. Generated HTML and JavaScript are never executed. See the contract and limitations.
  • Scheduled tasks — cron scheduling with concurrent-run protection, catch-up behavior, run history, and notifications.
  • Providers and skills — inspect pi configuration, check authentication with pi auth check, use atomic writes with backups, and import skills from GitHub, local directories, or npm commands.

Architecture

Specifications live in docs/: domain model, blueprint, API contract, and architecture decisions. They cover apply-on-spawn configuration, MCP registration through registerMcpServer, and the GitHub-backed board's single-writer model. The project uses strict TypeScript, Zod validation at boundaries, and a regression test suite.

Browser (React) → REST + SSE → Node server → pool of `pi --mode rpc` processes
                                  ↕ SQLite in ~/.cogitator + native pi files

License

MIT — © IgnitionAI