Skip to main content

Before you download

A desktop workspace where coding agents work as one team to plan, build, test, publish and maintain software. Workser adds shared project context and managed cloud services.
You can describe the work in plain language and review it in Preview. You still need to explain business rules, test important flows and decide what is ready. Complex or sensitive software may need a developer’s review.
Claude Code, Codex, Cursor Agent, GitHub Copilot and OpenCode, plus the built-in Workser Code agent. Each external CLI uses its own provider account and limits. Connect your agent.
Use the built-in Workser Code agent with credits for paid models, or configure OpenCode with a model available through your provider. A free OpenCode model depends on provider availability. Spark’s cloud trial is not an unlimited model allowance.
Yes. Assign a supported agent and model to each role, with instructions, skills, tools and references. The thirteen roles are grouped into Plan & design, Build, and Test, launch & improve. The AI team.
The current public download is for Macs with Apple silicon. Windows is on the waitlist. See Install & setup.

Plans and usage

The desktop app is free to download. Workser cloud plans start at $10/month. Connected coding agents use their provider accounts; the built-in agent uses Workser credits. Cloud overage and other hosted services can add usage charges. Full pricing guide.
No. A new organization gets 7 days of Spark free. Spark includes no monthly model credits; top-ups are available. Paid cloud features can pause when the trial expires without a subscription.
Actual reported model cost plus 15%, converted at 100 credits per dollar and rounded at settlement. A $1 model cost uses 115 credits. It is not a fixed per-step fee or a weekly allowance.
Yes. Custom domains are included in the current Spark offer. You purchase the domain separately and configure DNS. Cloud allowances.
Published rates are 1.25/GBfordatabasestorage,1.25/GB for database storage, 0.15/GB for files and $0.50/GB for egress. Automatic overage depends on the meters enabled for your organization. Project, app and team member limits require an upgrade. Cloud overage.
Published software runs on its hosting. Agent Cloud runs hosted product agents. Local coding agents need your Mac and required tools running to continue development.

Building and maintaining software

Roles, project channels, goals, tasks, documents, decisions, handovers, checks and managed deployment. The same project context helps you continue after the first release.
Yes. Agents can use authorized connections while developing or maintaining a project. Your software can call the same available actions from its backend using the SDK. Your app must enforce its own end-user permissions. App connections.
No blanket local-only promise applies. A connected agent sends model requests to its provider; the built-in agent uses Workser-managed model access. Shared project records, sync and deployment also use cloud services. Security & approvals.
Try the preview, inspect check evidence and approve the production release. Successful checks do not guarantee every business rule is correct. Preview & publish.
Yes. Preview on a device and use the available distribution routes. Store submission is currently disabled in the desktop release. Mobile apps.
No. Agent Cloud is a beta hosted runtime for agents inside your product. Each agent has a published configuration, selected models and bounded access to tools, connections and workflows. Your local coding-agent subscription does not pay for its hosted runs. Agent Cloud.
Workser Business documents the existing web platform, workflows and AI Employees. Computer Use is a separate desktop capability for screen and input tasks. They share your Workser account, but their execution and usage rules differ.

Troubleshooting

Workser Code checks two things: is the CLI on your PATH, and is it actually authenticated — by inspecting credential files, the OS keychain and environment variables.So an agent that’s installed but not signed in won’t appear as connectable. Run its own login command (claude /login, codex login, …) in a terminal, then re-check in Workser Code.Also confirm you’re using the CLI, not just the desktop app of the same name — Cursor’s CLI binary, for instance, is cursor-agent, not cursor.
The CLI can’t find the Workser Code daemon. Open Workser Desktop. If you’re running standalone or in CI, run workser login instead, then workser doctor to see what endpoint resolved.
Working as intended — something with a real consequence is waiting for you in Workser Code. Approve it there, then your agent retries. It’s not an error to work around.
Your agent tried something reserved for you: creating or switching a project, or deleting an environment variable. Do it yourself in Workser Code and carry on. See what your agent can never do.
No project is linked to this folder. Link it in Workser Code, or pass --project <id> explicitly.
You’re on a machine that has only the CLI and a token, so the file-based commands (checkpoint, restore, sync) can’t run. Every read-only command still works.
The session file records the endpoint it logged in against, so changing $WORKSER_ENV afterwards doesn’t move an existing session. Run workser login again, or pass --endpoint explicitly.
Both your folder and Workser changed, and sync stops rather than picking a winner. Resolve it in Workser Code rather than forcing it through.
Final, not retryable. A project’s region is fixed when it’s created, and the Neon backend (workser neon storage / functions) isn’t available in yours. Use the default bucket — workser storage — which every project has.
The classic one. A workflow feature is two-way: triggering it is the outbound half, and the workflow’s final node has to POST back to a webhook route in your app for the result to land anywhere. See the SDK’s workflows section.
Read the refusal and the operation it names. Agent permissions, protected paths and destructive-operation checks can stop a command. Do not bypass the refusal. Use the project’s migration and approval workflow for schema changes, and inspect Security & approvals.

Still stuck?

Install & setup

Installer, permissions and first-run troubleshooting.