What's new
in Worca.
Since 1.1.1 — pipelines you can export and share, runs that pause instead of dying, Ask Worca that reads your screenshots, and a server its own agents can't kill.
Your pipeline, in three formats.
Any saved Composer pipeline now leaves Worca — as a runnable Claude Code skill, as a JSON file another Worca user imports, or as a versioned plugin that bundles the agents and skills it depends on.
Built-in agents are never copied. A name clash on import becomes Name (2), never a replacement.
Export pipeline — the plugin form: a folder, a name, and whether a re-export bumps the version.
Runs pause. Only you stop them.
A model-side 500, a rate limit, an expired login — none of them end a run any more. The run pauses with its worktree intact, Resume retries the failed node in place, and the task source hears needs-human, not failed.
- 1The endpoint answers 500; Worca retries with backoff
- 2Budget exhausted — the run pauses, nothing is torn down
- 3Resume retries the node in place — the run finishes
Every site asks resolveFailure() for a verdict and enacts it. Shifting a case is a one-cell edit.
Drop in a screenshot. It sees it.
Images and PDFs attached to an Ask Worca message reach the model — stored raw on disk, read natively, never inlined into the prompt. And a chat can be pinned to a project or workspace, whatever page is behind it.
The composer: an attached PNG, the scope pinned to nimbus-crm, and the question — all before sending.
A spoofed body is refused before any write. SVG stays off the list — it is scriptable markup.
Agents can't kill the host.
On Aug 31 an implementer cleaning up test servers matched the production argv and killed the server orchestrating it. Every spawn now carries a hook that denies process-wide kills, the host PID in its env, and a preamble that names both.
ps aux | grep '[n]ode --disable' | … | xargs killBLOCKED · pipe-fedpkill -f server.mjsBLOCKED · process-widetaskkill /IM node.exeBLOCKED · by namekill 48213allowed · literal, not the host
Settings — Spawn diagnostics logs binary, argv and routing env per spawn, no restart needed.
Your endpoint, every code path.
Title generation used to hard-code a Haiku id. Now it follows the run's model, tier keys are filled in for endpoint-routed entries, and built-ins can be hidden from every picker when you don't use a first-party account.
Models — the catalog discloses endpoint-routed on the card; one checkbox hides built-ins everywhere.
First match wins
An install with no first-party model works with zero configuration. Effort stays low — the cheapest tier.
One command owns the UI.
worca ui start · stop · restart · status replace the twenty-line stack trace you got when the UI was already up. Already running is exit 0 and the URL; another program on the port is two lines and exit 1. And worca --version finally answers.
One UI per machine, by design: two instances would each spawn chat workers and fight over runs.
Shipped, tested, verified live.
