Add OpenClaw as an AI agent option - #9869
Open
mbot11 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add OpenClaw as an AI agent option
Summary
Adds OpenClaw (formerly Clawdbot/Moltbot) to the AI
coding-agent roster on
quattro, following the exact conventions of theexisting agents:
agent_package="npm:openclaw")omarchy-agent(openclaw tui, promptseeded via
--message)contract (
schemaVersion: 1), writingopenclaw.jsonnext toclaude.jsonandcodex.jsonWhy
OpenClaw is one of the most widely used agent harnesses, and its terminal UI
(
openclaw tui) is a full agent surface with tool approvals. Users who run italongside Claude Code / Codex / OpenCode currently get no agents-panel usage
tracking and no default-agent option. This patch closes both gaps the same way
every other agent is wired.
Changes
bin/omarchy-default-agent—openclaw/open-clawcase, usage stringsbin/omarchy-agent— launch case:openclaw tui(gateway-connected TUI),--message "$prompt"for prompt seedingdefault/omarchy/omarchy-menu.jsonc—setup.default.agent.openclawrowbin/omarchy-agent-usage-openclaw— new usage collector (same recordcontract as the packaged collectors; discovers sessions via
openclaw sessions --json --all-agentsand prompt counts from gatewayaudit events)
Notes for review
openclaw tuitalks to the local Gateway(loopback) and works headless, so the launch mapping needs no special flags.
openclawCLI rather than reading itsstate SQLite directly (the store uses the
sqlite-vecextension), whichalso keeps it stable across OpenClaw schema changes.
no message content, credentials, or provider keys are read or written.
Testing
bash -non both modified scripts; JSONC parse on the modified menuopenclaw tuilaunches against a running gateway and accepts--messageaggregates, atomic write to
~/.local/state/omarchy/agents/usage/openclaw.json