Skip to content

feat: allowlisted /api/agent/chat bridge for browser chat#2

Open
w1kke wants to merge 2 commits intocodex/m11-m23-tools-experience-enginefrom
feat/agent-chat-allowlist-2026-02-11
Open

feat: allowlisted /api/agent/chat bridge for browser chat#2
w1kke wants to merge 2 commits intocodex/m11-m23-tools-experience-enginefrom
feat/agent-chat-allowlist-2026-02-11

Conversation

@w1kke
Copy link
Contributor

@w1kke w1kke commented Feb 11, 2026

Summary

  • add POST /api/agent/chat backend route for browser chat integration
  • enforce strict action allowlist (chat.guide only)
  • default localhost-only guard (OPENCLAW_LITE_AGENT_CHAT_ALLOW_REMOTE=1 to override)
  • keep this endpoint browser-agent-only in non-test runtimes (BROWSER_AGENT_ONLY), with no dependency on another OpenClaw process
  • deterministic test-mode behavior in NODE_ENV=test
  • wire route in server/app.js and expose capability metadata
  • update specs (specs/02_api_contract.md, specs/04_tdd_milestones.md)
  • add e2e coverage (e2e/openclaw_lite/32_agent_chat_backend.spec.js)

Verification

  • npm test -- e2e/openclaw_lite/32_agent_chat_backend.spec.js e2e/openclaw_lite/31_backend_final_modularity_gate.spec.js

Scope clarification

This PR does not introduce a separate/main agent path.
OpenClaw Lite’s agent remains the in-browser agent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant