Account
Personal settings
Manage your account and execution credentials.
Platform
Platform admin
Platform-wide settings across all projects. Visible to platform admins only.
Daily Entry
Work Overview
Handle failed and pending-confirmation requirements first, then check in-progress items and recent results.
Scheduled jobs
Run prompts on a schedule or auto-dispatch SOPs to triage requirements, check projects, or summarize progress.
On schedule, scans this project’s requirements in the selected statuses that haven’t run an SOP yet, and dispatches the SOP once they pass the baseline gate. Each project uses one set of trigger settings.
Requirements & bugs
Requirements
See the result of each requirement. Open a failed one to see where it got stuck, then retry or edit.
Channels
Set up WeCom direct or group chat channels for task updates, then pick them in SOP settings or scheduled jobs.
AI assistant
The assistant you talk to in the AI workbench. Choose when it hands work to a role or an SOP, and the rules every conversation follows. This applies only to you.
RunsConcurrency rulesWhen running in the cloud,each project can run up to 10 SOPs at the same time; extras go to ‘Queued’ and start automatically in submission order when a slot frees up.Runs that failed, paused, are awaiting confirmation, or were canceled after starting still occupy a slot; only runs that completed successfully or were canceled while queued do not.Nested child SOPs are not counted separately; runs without a project share one pool of 10 slots.Personal runners are not subject to this limit; you can set a separate cap on the ‘Runners’ page.
Updating liveLogs, artifacts, and step details will appear here.
Needs a decision
Needs review
Runs pause here at human approval steps. Approve to continue or reject to rework according to the SOP.
Production SOPs
SOPs
SOP is a reusable AI workflow made of Agent, script and human-approval steps: give it a requirement and it produces documents, code or a PR step by step.
SOPs under “This project” are only used here. Once shared, other projects can pick them under “Team shared”. “Built-in” SOPs come with the platform; copy one into this project to run and edit it.
Configure this SOP's metadata, execution sandbox, preview archiving, and delivery metrics category
Sandboxes provide shared base tools and libraries; credentials are injected from the task assignee's personal token at run time.
Roles
Each role has its own tasks, artifacts, and gates. Project roles can be shared with other projects; SOPs only pick a role. These aren't edited on the canvas.
Usage
Project configuration
A project is the shared boundary for requirements, repositories, teams, and the default SOP. Click a project to open its settings.
Agent capabilities
Capability assets
Maintain MCP servers, rules and skills here; roles can use them once bound.
Runtime
Environment assets
Manage container build definitions for the current project.
From skillhub.cn Public skill library. Installing saves a snapshot of the selected version, which can be bound to roles and shared; when SkillHub publishes a new version, you’ll be notified here and can update manually.
Runners
Run tasks on your own computer or CVM; if no default is set, they run in the cloud.
Connect runner
macOS / Linux- 1Install CLIclaude / codex, etc.
- 2Run the connect commandBinding code is valid for 10 minutes
- 3Choose auth sourceLocal login or personal credentials
(curl -fsSL --connect-timeout 5 https:///runners/install.sh || curl -fsSL http:///runners/install.sh) | bash -s -- --server --token Generating… --service
Only connects out to the platform; no local ports are opened
Uninstall runner
(curl -fsSL --connect-timeout 5 https:///runners/install.sh || curl -fsSL http:///runners/install.sh) | bash -s -- --uninstall
My runners
0Access & platform
Access keys
Create and revoke access keys. REST API and MCP share the same key.