* Initial plan * chore: bump all workspace package versions from 0.2.5 to 0.3.0 Agent-Logs-Url: https://github.com/ComposioHQ/agent-orchestrator/sessions/da5b2769-e7d4-4d08-a60c-bd5f695d1ca7 Co-authored-by: harshitsinghbhandari <212377671+harshitsinghbhandari@users.noreply.github.com> * fix: update package-version test to expect 0.3.0 Agent-Logs-Url: https://github.com/ComposioHQ/agent-orchestrator/sessions/ad61e33e-417f-4482-b06c-0b60826b7f2d Co-authored-by: harshitsinghbhandari <212377671+harshitsinghbhandari@users.noreply.github.com> * chore: revert non-ao version bumps Only @aoagents/ao drives the 'ao update available' prompt (packages/cli/src/lib/update-check.ts compares against the @aoagents/ao registry version and reads the local @aoagents/ao package.json). All other workspace bumps are unnecessary. * chore: align workspace versions with npm registry Catch up source-of-truth package.json versions to what is already published on npm. The registry reflects releases done via Changesets; the in-tree files had drifted to 0.2.5. 0.2.5 -> 0.3.0: cli, core, web, agent-aider, agent-claude-code, agent-codex, agent-opencode, notifier-composio, notifier-desktop, notifier-slack, notifier-webhook, runtime-process, runtime-tmux, scm-github, terminal-iterm2, terminal-web, tracker-github, tracker-linear, workspace-clone, workspace-worktree 0.2.5 -> 0.2.6: notifier-discord, notifier-openclaw, scm-gitlab, tracker-gitlab 0.1.0 -> 0.1.1: agent-cursor Also updates agent-codex package-version.test.ts to expect 0.3.0. * test(cli): use future version in update-check cache test The cache-fresh test assumed getCurrentVersion() returned a value older than the cached latestVersion. With packages/ao now at 0.3.0 and resolvable from cli via pnpm's hoisted store at test time, getCurrentVersion() returns 0.3.0, so isOutdated against a cached latestVersion of 0.3.0 is false and the assertion fails. Use 99.0.0 in the cache so the comparison stays meaningful regardless of the current installed version. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: harshitsinghbhandari <212377671+harshitsinghbhandari@users.noreply.github.com> Co-authored-by: harshitsinghbhandari <claudeagain@pkarnal.com> |
||
|---|---|---|
| .. | ||
| src | ||
| CHANGELOG.md | ||
| README.md | ||
| package.json | ||
| tsconfig.json | ||
README.md
notifier-openclaw
OpenClaw notifier plugin for AO escalation events.
Quick setup
ao setup openclaw
This interactive wizard auto-detects your OpenClaw gateway, validates the connection, and writes the config. For non-interactive use (e.g., in CI/CD pipelines or automation scripts):
ao setup openclaw --url http://127.0.0.1:18789/hooks/agent --token YOUR_TOKEN --non-interactive
Required OpenClaw config (openclaw.json)
{
"hooks": {
"enabled": true,
"token": "<your-hooks-token>",
"allowRequestSessionKey": true,
"allowedSessionKeyPrefixes": ["hook:"]
}
}
AO config (agent-orchestrator.yaml)
notifiers:
openclaw:
plugin: openclaw
url: http://127.0.0.1:18789/hooks/agent
token: ${OPENCLAW_HOOKS_TOKEN}
Behavior
- Sends
POST /hooks/agentpayloads with per-session keyhook:ao:<sessionId>. - Defaults
wakeMode: nowanddeliver: true. - Retries on
429and5xxresponses with exponential backoff.
Token rotation
- Rotate
hooks.tokenin OpenClaw. - Update
OPENCLAW_HOOKS_TOKENused by AO. - Verify old token returns
401and new token returns200.
Known limitation (Phase 0)
- OpenClaw hook ingest is not idempotent by default. Replayed webhook payloads are processed as separate runs.
- Owner: AO integration.
- Follow-up: add stable event id/idempotency key support.