Integrations

Connect Hiloop to your existing agent platforms and team tools. Interactions flow through the same encrypted pipeline regardless of where they originate.

Claude Code

Connect Claude Code to Hiloop with a lightweight daemon plugin. Every tool call, file edit, and terminal command streams to your Hiloop app in real time -- and you can approve, deny, or guide the agent directly from the UI.

Install

Install the plugin globally, then configure it with your API key.

terminal
npm install -g hiloop-claude-code

# Configure with your API key (from Admin > Agents)
hiloop-claude-code config hlp_your_api_key my-agent

# Install hooks into Claude Code
hiloop-claude-code install
Configuration is saved to ~/.claude/hiloop.json
Hooks are added to ~/.claude/settings.json automatically

Run

Start Claude Code with the Hiloop daemon. Everything Claude does streams to your Hiloop app.

terminal
# Start Claude Code + daemon together (uses tmux)
hiloop-claude-code run

# Or start the daemon separately
hiloop-claude-code start

How it works

1 The daemon hooks into Claude Code's event system -- every tool call, file edit, and command is captured automatically.
2 Events are converted to rich Hiloop components -- code blocks, diffs, file trees, execution output, and more -- and sent to your session in real time.
3 When Claude needs permission (file writes, bash commands), the request appears in Hiloop with Approve / Deny buttons. Your decision flows back instantly.
4 You can send messages from Hiloop to give Claude new instructions, ask questions, or redirect its work -- all via the chat interface.

What you see

The plugin automatically converts Claude Code events into rich visual components:

Claude Code event Hiloop component
Bash command + outputexecution block with status
File write / editfile_content or diff block
File read / searchfile_content with syntax highlighting
Permission requestbutton_group (Approve / Deny / Always)
Agent thinkingthinking accordion
Task progresssteps or task_list
Session endSession auto-closes

No changes to your agent needed. The plugin hooks into Claude Code's native event system. Your existing prompts, CLAUDE.md files, and workflows work exactly as before -- with full Hiloop visibility on top.

OpenClaw

Add Hiloop as a channel in OpenClaw. Your agent gets approvals, reviews, forms, notifications, and payments -- plus dedicated tools through the channel interface.

Install

terminal
npm install hiloop-openclaw

Configure

Add the Hiloop channel to your openclaw.json:

openclaw.json
{
  "channels": [
    {
      "type": "hiloop",
      "apiKey": "hlp_xxx"
    }
  ]
}
apiKey -- your agent API key (required, starts with hlp_)
baseUrl -- Hiloop API URL (default: https://api.hi-loop.com)
pollIntervalMs -- how often to check for new messages (default: 2000ms)
defaultPriority -- default priority: critical, high, normal, low

Available tools

Once loaded, your OpenClaw agent automatically gets these 8 tools:

Tool Description
create_interaction Create an approval, review, form, or chat interaction
await_response Long-poll for the human's response (up to 30s)
cancel_interaction Cancel a pending interaction
acknowledge_interaction Acknowledge receipt of an interaction
send_message Send a message within an interaction
list_messages List messages for an interaction
list_interactions List all interactions for the agent
get_interaction Get the current status of an interaction

Message flow

AUTHORIZE request
OpenClaw sends an AUTHORIZE request → Hiloop creates an approval interaction → human sees it in the Hiloop app
Human responds
Human approves or declines in Hiloop → channel polls API → result returned to the OpenClaw agent
Structured interactions
Agent calls create_interaction → creates interaction → await_response → gets human decision

Example: approval gate

Gate dangerous actions behind human approval in an agent workflow:

Agent workflow
// Agent wants to deploy to production
1. create_interaction(
     type: "approval",
     title: "Deploy v2.3 to production",
     options: ["Approve", "Deny", "Defer"],
     priority: "high",
     deadlineMinutes: 60
   )
   -> { interactionId: "abc-123" }

2. await_response(interactionId: "abc-123", timeout: 30)
   -> { status: "responded", response: "Approve" }

3. If approved, proceed with deployment.

Warp Oz

Warp Oz coding agents request human review via webhooks. When an Oz session needs human input -- code review, deployment approval, or guidance -- it sends a webhook event to Hiloop.

Setup

  1. Create an API key -- go to Settings → Agents → New Agent in Hiloop. Note the key (starts with hlp_).
  2. Configure the webhook URL -- in your Oz agent settings, add https://api.hi-loop.com/v1/integrations/warp-oz/webhook as a webhook destination.
  3. Set the environment variable -- your Oz agent needs the key at runtime.
Environment variable
export HILOOP_API_KEY="hlp_your_api_key_here"

Webhook flow

1 Oz agent sends a review request to the Hiloop webhook endpoint.
2 Hiloop creates an interaction and notifies the human reviewer.
3 Human reviews and responds (approve, request changes, comment).
4 Hiloop sends the response back to the webhook callback URL.

Session tracking

Hiloop links interactions to Oz sessions via the session_id field. Use the sessions endpoint to list all interactions tied to a specific Oz coding session, providing full context for multi-step reviews.

curl
curl https://api.hi-loop.com/v1/integrations/warp-oz/sessions/{session_id} \
  -H "X-API-Key: hlp_your_key"

API endpoints

POST /v1/integrations/warp-oz/webhook Submit webhook event
POST /v1/integrations/warp-oz/webhook/batch Batch submit events
GET /v1/integrations/warp-oz/interactions/:id Get interaction status
GET /v1/integrations/warp-oz/interactions/:id/await Long-poll for response
POST /v1/integrations/warp-oz/interactions/:id/messages Send message
GET /v1/integrations/warp-oz/interactions/:id/messages List messages
GET /v1/integrations/warp-oz/sessions/:sessionId List session interactions
DELETE /v1/integrations/warp-oz/interactions/:id Cancel interaction
GET /v1/integrations/warp-oz/info Integration metadata