Before you download
What is Workser Code?
What is Workser Code?
Do I need to know how to code?
Do I need to know how to code?
Which agents can I use?
Which agents can I use?
What if I do not have an AI subscription?
What if I do not have an AI subscription?
Can I use different agents for different roles?
Can I use different agents for different roles?
Which computers are supported?
Which computers are supported?
Plans and usage
What am I paying for?
What am I paying for?
Do I need a card for the trial?
Do I need a card for the trial?
How are built-in agent credits calculated?
How are built-in agent credits calculated?
Can Spark use a custom domain?
Can Spark use a custom domain?
What happens above the cloud allowance?
What happens above the cloud allowance?
Does it keep working when I close my Mac?
Does it keep working when I close my Mac?
Building and maintaining software
What does Workser add to a coding agent?
What does Workser add to a coding agent?
Can agents use my apps, and can my software use them too?
Can agents use my apps, and can my software use them too?
Does all my code stay on my machine?
Does all my code stay on my machine?
What happens before an app goes live?
What happens before an app goes live?
Can it build a mobile app?
Can it build a mobile app?
Is Agent Cloud a hosted Codex or Claude subscription?
Is Agent Cloud a hosted Codex or Claude subscription?
How does this relate to Workser Business and Computer Use?
How does this relate to Workser Business and Computer Use?
Troubleshooting
Workser Code doesn't see my agent
Workser Code doesn't see my agent
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.not_connected (exit 4)
not_connected (exit 4)
workser login instead, then workser doctor to see what endpoint resolved.awaiting_approval (exit 5)
awaiting_approval (exit 5)
owner_only (exit 6)
owner_only (exit 6)
no_project
no_project
--project <id> explicitly.needs_local_app
needs_local_app
checkpoint, restore, sync) can’t run. Every read-only command still works.workser doctor points at the wrong environment
workser doctor points at the wrong environment
$WORKSER_ENV afterwards doesn’t move an existing session. Run workser login again, or pass --endpoint explicitly.sync says diverged
sync says diverged
regionSupportsNeonBackend: false
regionSupportsNeonBackend: false
workser neon storage / functions) isn’t available in yours. Use the default bucket — workser storage — which every project has.The workflow runs but nothing appears in the app
The workflow runs but nothing appears in the app
A shell command or SQL statement was refused
A shell command or SQL statement was refused

