Getting Started

Use this path when you want to record a real local agent session.

Install dependencies

bun install

Configure the web app

Create local environment values for the web app:

NEXT_PUBLIC_APP_URL=https://looma-gold.vercel.app
NEXT_PUBLIC_SUPABASE_URL=<your-supabase-url>
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY=<your-publishable-key>
SUPABASE_SERVICE_ROLE_KEY=<your-service-role-key>
OPENAI_API_KEY=<your-openai-api-key>

SUPABASE_SERVICE_ROLE_KEY and OPENAI_API_KEY are server-only values. Do not expose them in browser code or commit them to the repository.

Run Looma

bun dev

Open /dashboard.

Sign in

Create or use a Supabase-backed account. Dashboard and sessions routes require a signed-in user.

Create an API key

From the dashboard, open the recording setup flow and create a Looma API key. The key is shown once. Use it as LOOMA_API_KEY when configuring agent tooling.

export LOOMA_API_URL=$NEXT_PUBLIC_APP_URL
export LOOMA_API_KEY=<token>

Connect Claude Code

Install the public beta bridge, write Claude Code MCP and hook config, then run the end-to-end doctor check:

npm i -g looma-agent@beta
looma setup claude-code --app-url $NEXT_PUBLIC_APP_URL --api-key <token>
LOOMA_API_URL=$NEXT_PUBLIC_APP_URL LOOMA_API_KEY=<token> looma doctor --e2e

The setup command writes .mcp.json and .claude/settings.local.json in the Claude Code project. Restart Claude Code, run /mcp, and confirm the looma server exposes record_start, record_event, and record_stop.

Verify the local app

Before connecting an agent, make sure these routes load:

• /dashboard
• /sessions
• /sessions/demo