Create and manage tickets from any page. Grab page info, console errors, and screenshots straight into a ticket — no context-switching required.
Download, unzip, then load in Chrome: chrome://extensions → Developer mode → Load unpacked.
Re-run the setup wizard to reconfigure your workspace name, departments, git settings, or create a new first project.
This will reset your onboarding status and redirect you to the setup wizard.
Set the human-facing identity Stoaria uses for prompt context and platform display.
Set the company name Stoaria uses in prompt context and generated agent files.
Choose the department, agent, or human responsible for incoming issues, decomposition, and initial assignment.
Archive done and canceled issues after separate close-age delays.
Configure platform model providers, harness routing, complexity categories, and per-model concurrency.
Model slugs can be provider/model or provider/subprovider/model. Two-part slugs use the provider as the subprovider.
Build reusable paths from Stoaria to an agent environment by mixing ordered connection cards.
Global Stoaria connections available to all users and agents.
Register external MCP servers to route through Stoaria. Configured tools will be available to connected clients.
Configure text Stoaria prepends before agent messages.
Define categories, map role levels, and choose primary plus secondary models. Agent runtime routing is not wired to this yet.
Configure company issue types, whether they usually involve code, and human notification behavior.
Company-level default templates. Fields support Stoaria Jinja variables.
Reusable webhook destinations. URL, auth details, and payload all support Stoaria Jinja variables.
Configure issue-type based notification targets, elapsed-time reminders, repeat cadence, and webhook destinations. Webhook fields support Stoaria Jinja variables.
Company-level policy hints for risky git, delete, shell, and repository behavior.
Configure ordered deterministic dispatch priority rules. Milestone options are included ahead of milestone support.
Configure workflow stages and entry gate requirements.
Choose who can start, stop, restart, or rebuild this tenant environment from Stoaria.
Set the OpenClaw Control UI / host surface used by Stoaria links.
Global process guidance Stoaria can prepend to issue-scoped agent messages.
Composio credentials are tenant-owned Stoaria secrets. OpenClaw should consume them only through the stoaria-composio MCP.
Store COMPOSIO_API_KEY in the tenant OpenBao config. Do not register a direct mcp.servers.composio key in OpenClaw.