Documentation

Hem docs

Connect Hem, work history for coding agents, to any MCP agent.

Quickstart

Sign in to Hem and get an API key from the usage dashboard.
Add the Hem MCP server to your agent config (snippets below; package ID still pending).
Run a task with your agent as usual.
Open the dashboard to see the structured events.

# Claude Code · MCP config shape (ID pending)
{
  "mcpServers": {
    "hem": {
      "command": "npx",
      "args": ["[PACKAGE_ID]"]
    }
  }
}

# Codex · MCP config shape (ID pending)
{
  "mcpServers": {
    "hem": {
      "command": "npx",
      "args": ["[PACKAGE_ID]"]
    }
  }
}

# Any MCP-capable agent · config shape (ID pending)
"hem": { "command": "npx", "args": ["[PACKAGE_ID]"] }

Final package ID is not locked yet. Snippets use [PACKAGE_ID] as a placeholder.

Tools reference

report_usage

How the agent records a structured work event (task started, decision, correction, outcome, and similar).

list_events

Pull your history. Runs only when you ask for it — Hem never injects history automatically.

delete_task_usage

Erase recorded events. You can remove any of them, or all of them.

Event types

Each event is short, structured, and readable on its own. Examples below are labeled illustrative.

Example

task.startedBegin a unit of work

task.completedWork finished successfully

task.failedWork ended in failure

task.abandonedWork paused or left unfinished

decisionA choice that shaped the approach

correctionYou steered the agent back

tool.summaryShort note on a tool run

interactionA notable exchange in the work

Episodes & patterns

Events roll up into episodes (one per unit of work) and patterns (what keeps recurring across episodes). Both ship today. Use list_events when you want to look back.

Shipped

HTTP service

The MCP server sits on top of an HTTP service. Endpoint docs are coming.

Coming soon

Not yet

For an honest split of what ships today versus what we're building toward, see the homepage section Here's what works now.