hipmmcode agent

hipmmcode is the Rust agent kernel that powers Agent mode on the platform. Most users never interact with it directly — when you toggle 🤖 Agent, the platform runs a hipmmcode turn for you and streams the result back. This page is for advanced users who want to drive the agent from their own tooling.

What the platform does with it

In Agent mode, each turn is delegated to hipmmcode:

your message ──► platform ──► hipmmcode (one turn)
                                 │  multi-step tools + skills
                                 │  grounded in your knowledge base
                                 ▼
                          text · tool calls · generated files
                                 │  streamed as it happens
             browser / IM ◄──────┘

The agent runs with your project's knowledge base available, produces real documents (DOCX/PPTX/XLSX/PDF), and streams events as they occur.

Driving hipmmcode yourself

If you run hipmmcode locally or in your own environment, it exposes a few integration surfaces:

Self-documenting integration guide

hipmmcode ships its integration manual inside the binary. On any machine that has it installed:

hipmmcode integration

This prints the exact contract for that binary version — the fastest way for you (or an LLM building on top of it) to bootstrap an integration without hunting through source.

Headless one-shot (exec)

Run a single agent turn non-interactively and get structured output:

hipmmcode exec -p "summarize the repo and list risks" \
  --output-format stream-json

• --output-format stream-json emits newline-delimited JSON events (text, tool calls, tool results, final result) — ideal for piping into another program.
• Use plain text output for a simple string, or JSON for a single structured result.

Long-running server (serve)

Run hipmmcode as an HTTP/WS service with an async task queue:

hipmmcode serve

• Submit a task and get an id back immediately; poll or receive a webhook when it finishes — good for "fire a job from my phone, collect the result later."
• Keeps a persistent agent available to multiple callers.

How this relates to the platform

The platform's Agent mode is essentially the managed version of the above: it spawns a hipmmcode stream-json turn per message, injects your knowledge base, enforces per-user isolation and concurrency limits, and renders the streamed events as chat. If you're happy using the browser or IM, you never need to touch the CLI — but the same engine is available directly when you want to embed it.

Next

• Agent mode — the no-setup way to use this from the platform.
• API keys — credentials for programmatic access.
• FAQ.