Sero CLI
sero-cli is Sero's workspace/session command surface. Agents call it as a tool, and operators can use the same syntax in Sero-aware terminal contexts.
Scope and syntax
- A leading
serotoken is optional for command resolution, but examples use it for clarity. - Commands run in the current workspace and, when invoked during an agent turn, the current session/turn.
- Invocation sources are
tool,bash, andterminal. - Session-owned plugin/extension commands only appear for the active scoped session.
- Blacklisted command roots are not registerable:
auth,safeStorage,net,layout,agent,github.
Batch behavior
sero-cli accepts multiple commands, one per line. Execution stops on the first non-zero exit code or timeout.
Non-terminal invocations truncate output at 50KB / 2000 lines. Multi-command batches omit rich image output; rerun screenshot commands alone to receive images. Interactive commands disable normal per-command timeout behavior.
Built-in namespaces
workspace
devserver
See Containers and Dev Servers.
app
See Browser and Capture. app commands are UI-backed and depend on the renderer app panel being visible.
browser
See Browser and Capture. browser controls the visible in-app browser tabs, not arbitrary hidden browser automation.
Tabs are workspace-owned and loaded lazily through the browser panel. Explicit tab ids cannot cross workspace boundaries.
editor
terminal
vcs
session and set-title
appstate
appstate is JSON state only; it is not UI automation.
artifacts
Plugin-bridged commands
Sero bridges selected extension tools and commands into sero-cli so agents use one command surface.
- Core tools such as
todo,memory,question,cron,git_manager, and others are allowlisted. - Plugin packages can opt into bridging with
sero.plugin.bridgeToolsmetadata. researchis explicitly not bridged.- Admin tooling is intentionally not agent-accessible through this bridge.
- Session-owned bridged commands are visible only for the matching active session scope.
- For JSON-heavy bridged commands, run
sero help <command>first and follow the reported schema.