Menu
Cut an AgentOS release via the scripts/publish flow. Use when the user asks to release, publish, cut a release, or bump the AgentOS version.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Compare GigaCode's OpenCode-compatible HTTP/SSE API with native OpenCode in isolated temporary workspaces. Use when asked to sanity-check, re-test, or manually validate Claude Sonnet streaming, multi-turn sessions, tool calls, permissions, file edits, cancellation, or post-cancel reuse.
Audit AgentOS ACP feature coverage across the stable ACP v1 specification, each underlying agent harness and control interface, its upstream ACP adapter, and AgentOS public API/types. Use for ACP upgrades, adapter parity checks, or missing-feature audits.
Publish @agentos-software/* registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.
Cut an AgentOS release-preview. Use when the user asks for a preview, release-preview, or a branch dist-tag build.
Run the deferred AgentOS E2E smoke test from public npm packages. Use when the user asks to sanity check, smoke test, or verify a release works.
Use the browse CLI for Browserbase browser automation, Browserbase cloud APIs, Browserbase Functions, templates, web fetch/search, diagnostics, and Browse.sh skill discovery/installation. Use when the user asks to navigate pages, inspect browser state, run local or remote browser sessions, manage Browserbase resources, call Browserbase Functions, browse or scaffold Browserbase templates, fetch or search web content, diagnose browse setup, find or install a skill for a website task, discover site-specific Browse.sh skills, or install/refresh this browse skill.
| name | release |
| description | Cut an AgentOS release via the scripts/publish flow. Use when the user asks to release, publish, cut a release, or bump the AgentOS version. |
The publish flow lives in scripts/publish and is driven by
.github/workflows/publish.yaml.
AgentOS is the source of truth. It publishes npm packages, crates, runtime
sidecars, Pyodide/R2 assets, and @agentos-software/* registry packages from
this repository. secure-exec releases are generated compatibility shims that
follow the AgentOS version; never release secure-exec first.
merge-aos or main bookmark.just release --version 0.2.0 # exact version
just release --version 0.2.0-rc.1 # rc (npm tag `rc`)
just release --patch # semver bump from latest git tag
run=$(gh run list -R rivet-dev/agentos --workflow=publish.yaml -L1 --json databaseId --jq '.[0].databaseId')
gh run watch -R rivet-dev/agentos "$run" --exit-status
publish.yaml.scripts/publish/src/local/cut-release.ts is a pure trigger; version changes
happen in the ephemeral CI checkout.workspace:* deps are rewritten to literal versions by the publish bump pass.