fix(skills): retarget openclaw-orchestrator and /spawn at the current CLI - #90
fix(skills): retarget openclaw-orchestrator and /spawn at the current CLI#90willwashburn wants to merge 2 commits into
Conversation
|
Warning Review limit reached
Next review available in: 58 minutes Limit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (10)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: aec62d675f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
All reported issues were addressed across 10 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
…tokens The three pattern skills each mandated printing the raw workspace key in an observer URL — "Do not print a placeholder — print the real URL the user can click. This is mandatory." A workspace key is an administrative credential; a URL query string is the worst place to put one. They also required the key be copied into every worker prompt. That is unnecessary: `create_workspace` and `set_workspace_key` both pin the workspace to the project, and the relay MCP server a `relay-worker` subagent starts resolves that pin on its own. The mandate put an admin credential into N prompts and N transcripts to achieve nothing. - Step 3 now calls `get_observer_url`, which mints a scoped, expiring, read-only token. Requires the tool added in AgentWorkforce/relay#1422. - Worker prompts no longer carry the workspace key; the worker agent definition and SubagentStart hook now say the workspace is inherited and that a key must never be printed or requested. - The three skills' shared setup steps are now byte-identical, and all three carry the worker/stage tracking table and the "do not self-release" instruction that only relay-team had. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Jmke9G9s7ftrN49opNmdx1
… CLI `openclaw-orchestrator` documented Agent Relay's removed flat command surface almost end to end: `agent-relay up`, `spawn`, `agents`, `agents:logs`, `agents:kill`, `send`, `inbox`, `down`, plus `mcporter call relaycast ...` for channels and messaging. None of those are registered at the top level any more — `createProgram()` puts lifecycle under `agent-relay node ...` and messaging under `agent-relay message ...`, with the old flat group surviving only as a hidden, deprecated `local` alias. It also documented a `--team` flag that `node agent spawn` does not have; grouping is by `--channels`. Rather than re-document what `orchestrating-agent-relay` already covers correctly, this reduces the skill to what is actually OpenClaw-specific (the `@agent-relay/openclaw` setup, `openclaw system event` completion reporting, provider quirks) and defers everything else to that skill. It also names the removed commands explicitly so an agent carrying them in context discards them. Other fixes: - Frontmatter `name:` was `agent-relay-orchestrator` while the published package and directory are `openclaw-orchestrator`, so the installed skill registered under a name nothing referenced. Also drops the non-contract `version:`/`homepage:`/`metadata:` keys. - `/spawn` used the same removed commands, told the user to supply a workspace key that `node up` auto-creates, and pointed monitoring at `agents:logs`. Retargeted, and it now offers an observer link. - `/create-workflow` referenced `agent-relay agents`. Every command in the rewritten files was checked against `--help` on a build of the current CLI. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Jmke9G9s7ftrN49opNmdx1
aec62d6 to
287c6e8
Compare
2 participants
Summary
openclaw-orchestratordocuments a CLI that no longer exists. Nearly every command in it is wrong:agent-relay up --workspace-key … --no-spawnagent-relay node up --backgroundagent-relay spawn NAME CLI "task"agent-relay node agent spawn <cli> --name … --task …agent-relay agentsagent-relay node agent listagent-relay agents:logs NAMEagent-relay node tail --agent NAMEagent-relay agents:kill NAMEagent-relay node agent release NAMEagent-relay send '#chan' 'msg'/agent-relay inboxagent-relay message post/message inbox checkagent-relay downagent-relay node downmcporter call relaycast create_channel--channelson spawn--team TEAM--channelscreateProgram()inpackages/cli/src/cli/bootstrap.tsregisters none of those at the top level. Lifecycle lives underagent-relay node …, messaging underagent-relay message …, and the old flat surface survives only as a hidden, deprecatedlocalalias that prints a removal warning.Rather than re-document what
orchestrating-agent-relayalready covers correctly, this reduces the skill to what is genuinely OpenClaw-specific — the@agent-relay/openclawsetup,openclaw system eventcompletion reporting, provider quirks — and defers everything else to that skill. It names the removed commands explicitly, so an agent that has them in context from an older copy discards them rather than trusting them.Alternative worth considering: delete the skill outright. Its unique content is now about 30 lines, and everything else duplicates
orchestrating-agent-relay. I kept it because it's a published package (@agent-relay/openclaw-orchestrator) and removing one is your call, not mine.Also fixed
name:wasagent-relay-orchestratorwhile the directory and published package areopenclaw-orchestrator, so the installed skill registered under a name nothing else referenced. Also drops the non-contractversion:/homepage:/metadata:keys./spawnused the same removed commands, told the user to supply a workspace key thatnode upauto-creates, and pointed monitoring atagents:logs. Retargeted; it now also offers an observer link and warns against reading replies withnode tail./create-workflowreferencedagent-relay agents.prpm.json+ README:openclaw-orchestrator1.0.0 → 2.0.0 (rewrite),/spawn1.0.0 → 1.1.0,/create-workflow1.0.4 → 1.0.5.Part of a series from a review of the Agent Relay skills and plugins.
Test Plan
node agent spawn,node agent list,node agent attach,node agent release,node status,node up,message inbox check,observer— all return help, none errornode agent spawn --helpthat the flags are--name/--channels/--task/--modeland that no--teamflag existsagent-relay --helpthat the top-level surface has noup,spawn,agents,send, ordownprpm.jsonparses as valid JSON after the version bumpspackage.json, no CI workflows)Screenshots
n/a
Generated by Claude Code