Memory & Observability

What “connected” means

Your agents run in isolated microVMs. Memory and Observability are optional sidecar microVMs you buy, then connect (grant) to agents you own. Until you connect them, the agent does not see that sidecar.

Buy and connect are separate steps:

1. Buy — provision the sidecar VM (usually in the dashboard).
2. Connect — grant that sidecar to a specific agent VM (dashboard, CLI, or MCP).

A connection from the UI shows up in jurniti memory ls. A CLI grant shows up on the Memories page. Same control plane.

How to connect memory

A. In the browser (dashboard)

You need at least one agent already running (see Quickstart).

B. From the CLI

Prerequisites:

• CLI installed and logged in (jurniti login)
• A read-write API key (read-only keys can list, not connect)
• A memory already bought (step A.2, or any existing connection from jurniti memory ls)

# 1. See connections (ids look like mcpc_…) and which agents already have them
jurniti memory ls

# 2. Find the agent VM id
jurniti vms ls
# pick a row that is an agent (Hermes, Claude Code, …), not the memory VM

# 3. Connect
jurniti memory grant --connection mcpc_YOUR_ID --vm vm-YOUR_AGENT_ID
# → granted connection mcpc_… to agent vm-…

# 4. Confirm
jurniti memory ls
# GRANTED_VMS column should list vm-YOUR_AGENT_ID

# Disconnect later
jurniti memory revoke --connection mcpc_YOUR_ID --vm vm-YOUR_AGENT_ID

Example shape:

jurniti memory ls
# ID                             NAME              PROVIDER         GRANTED_VMS
# mcpc_19ef3c3cc443ea7dea465a68  memory-vm-…       memoryobsidian   -

jurniti memory grant \
  --connection mcpc_19ef3c3cc443ea7dea465a68 \
  --vm vm-68648d6a5722293cc9f7c740
# granted connection mcpc_19ef3c3cc443ea7dea465a68 to agent vm-68648d6a5722293cc9f7c740

Buying the memory VM itself is still done in the dashboard today; the CLI covers list / connect / disconnect.

C. From MCP (your coding agent)

Mount the CLI once so your agent inherits your login — see MCP:

claude mcp add jurniti -- jurniti mcp
# or: codex mcp add jurniti -- jurniti mcp

Then use these tools (same outcomes as the CLI / UI):

Example tool call to connect:

{
  "connection_id": "mcpc_19ef3c3cc443ea7dea465a68",
  "vm_id": "vm-68648d6a5722293cc9f7c740"
}

• Discover connection_id with mcp_connections_list (or jurniti memory ls).
• Discover vm_id with vms_list (or jurniti vms ls).
• Use a read-write key for grant/revoke; list works with read-only.

Your agent operates as you (tenant-scoped). Wrong-role targets fail with the same invalid_agent error as the dashboard.

How to connect observability

Same pattern as memory: buy sidecar → grant to agent.

Browser

1. Open Observability
   (/dashboard/observability).
2. Buy Latitude or Langfuse (checkout → sidecar microVM).
3. On the sidecar card, connect agents with the grant controls (same idea as Memories’ Connect / Disconnect).
4. v1 keeps one active observability grant per agent.

CLI

jurniti observability ls

# --sidecar = observability VM id; --vm = agent VM id
jurniti observability grant --sidecar vm-SIDE --vm vm-AGENT
jurniti observability revoke --sidecar vm-SIDE --vm vm-AGENT

MCP

{
  "sidecar_vm_id": "vm-…",
  "agent_vm_id": "vm-…"
}

Quick comparison

After you connect

1. Control plane stores the grant (tenant-scoped).
2. Platform injects config into the agent guest (memory: MCP connections file; observability: observability / OTEL file).
3. The harness applies its native config when it supports auto-wire (Hermes, Claude Code, Codex, OpenClaw, OpenCode, OpenHands, Goose, DeepAgents, Gemini CLI, …).

You do not SSH in to paste tokens for the platform-managed path.

Which agents auto-wire memory MCP?

Buy is dashboard-only for memory and observability SKUs. Connect works from the dashboard, jurniti memory / jurniti observability, and customer MCP tools — same grants.

Auto-wire (guest config written from the inject file) requires a real MCPClientConfigurer (or telemetry configurer for observability). Agents that have no file-based remote MCP config today are listed with reasons in the test inventory unsupportedMCPClients in internal/harness/mcp_client_configurer_test.go (examples: pi, grok, paperclip, aider, and similar). That list is the single source of truth — we do not stub empty configurers to green a matrix cell. Closing a gap means implementing a real merge script and removing the harness from that map.

Telemetry (observability) is separate: agent harnesses implement TelemetryConfigurer (or use the default apply script); sidecar engines never consume grants as agents.

CLI demo

Live attach recording (list → grant → list + MCP help):

• GIF: jurniti-memory-attach-demo.gif
• MP4: jurniti-memory-attach-demo.mp4

Related