Worca
changelog · v1.9.0 → v1.10.0
What's new · v1.10.0

Publish now.
PR later.

Share a run's branch before any pull request, ship to Azure DevOps too, give agents your team's skills, and hear from Worca when a run needs you.

Publish branchAzure DevOpsSkillsDesktop alertsWorkspace AutoGuardrails
A finished run's page with Create PR and Publish branch in its header, and the Publish branch dialog open: the run's branch, Push to origin, Publish
NewPublish branch
NewAzure DevOps
Shipping

Publish a branch without a pull request.

Want a teammate or CI to try a run's work before anyone reviews it?
Now press Publish branch: Worca pushes the branch and opens no pull request. Fix what testing finds, press Push changes, and open the pull request when it is ready, as a draft if you like.

no pull request openedfixes push to the same branchopen PRs as draftsmerging closes the issue
From finished run to merged
  1. 1Publish branch: the branch is on origin, no pull request yet
  2. 2A teammate or CI checks it out and tests it
  3. 3You fix what they found and press Push changes
  4. 4Create PR, ticked Open as draft
  5. 5The merge closes the issue the run came from

Workspace runs publish one branch per project, each with its own tick.

The Ship it dialog for the CSV export run: push to origin, open the PR in origin, a written description, and Open as draft ticked

Ship it: the pull request can now open as a draft.

Azure DevOps

Azure DevOps works like GitHub.

Is your code on Azure DevOps instead of GitHub?
Now Worca clones, pushes and opens pull requests there too, with one personal access token. Team metrics see your merges, and a new plugin picks tasks from Azure Boards.

pull requests, drafts includedclone by URLAzure Boards as a task sourceagents never see the token
Every URL form, one repository
httpsdev.azure.com/acme/Nimbus/_git/nimbus-crm
sshssh.dev.azure.com:v3/acme/Nimbus/nimbus-crm
older hostacme.visualstudio.com/Nimbus/_git/nimbus-crm
Worca seesacme/Nimbus/nimbus-crm

Clones, pushes and team metrics all agree it is the same repository.

A work item, start to finish
  1. 1Pick a work item from Azure Boards as the task
  2. 2The run works on it
  3. 3Create PR opens the pull request in Azure DevOps
  4. 4The pull request links the work item
  5. 5The work item closes when the run completes, if you turn that on
Skills

Give every agent your team's skills.

Want your agents to follow the same checklists and style guides every time?
Now import a skill from a folder, a git URL or a pasted SKILL.md, add it to a set, and every run and Ask Worca chat on that set's projects can use it. Nothing is written into your repository.

import from a folder, git or pasterisky files flagged before importswitch a skill off for one runupdates only when you say so
The Import skill preview for deploy-checklist: its name, three files with a shell block and an executable flagged, the limits, and the notice about what agents may run

Import preview: every file, with anything that runs flagged.

Checked before it reaches your agents
scripts/preflight.shEXECUTABLE
!`git branch --show-current`SHELL BLOCK
hooks:DECLARES HOOKS
Agents call it by its set/general:deploy-checklist
Alerts

A desktop alert when a run needs you.

Ever found a run that had been waiting on you for an hour?
Now Worca can show a desktop notification when a run stops for a question, an approval or a decision, and puts a count on its browser tab. Click the notification to open the run.

macOS · Windows · Linuxonly when you are elsewhereno question text on the lock screenoff until you turn it on
While you work in another app
(2) Worca CC
Worca: Approval neededWebhooks for deal stage changes
now

Answer the question and the notification goes away.

Settings, General: the new Alerts card with Desktop notifications, Badge when something is waiting switched on, and Send test notification

Settings › General › Alerts, set per browser.

Workspaces

Auto picks the workflow for workspaces too.

Running one task across several repositories?
Now start a workspace run on Auto and Worca reads every project, proposes a workflow that plans and reviews per project, and waits for your OK. Branches are made only in the projects the run changes.

reads every member projectplans per projectno empty branchesone pull request per changed repository
Review the workflow for a workspace run on Auto: Clarify, Plan, Refine Plan, Implementation and Review Implementation, the middle steps marked per project

Auto's proposal for the Nimbus workspace: steps run per project.

Branches only where work happened
nimbus-crm · 3 fileswaitingbranch + pull request
nimbus-web · 2 fileswaitingbranch + pull request
nimbus-jobs · no changeswaitingno branch

an untouched project keeps no branch to clean up

Guardrails

Agents can't touch Worca's own files.

Worried a prompt-injected agent could rewrite the tool that runs it?
Now the Normal and Strict guardrails keep agents out of Worca's database, settings and secrets, and away from its plugins and scripts. Strict also blocks the network commands it missed before.

database and secrets: no readingplugins and scripts: no editing13 more network commands blockedhosted folder browser limited
Normal and Strict, now
read ~/.worca-cc/worca-cc.dbDENIED
read plugins/*/data/secrets.jsonDENIED
edit ~/.worca-cc/scripts/deploy.mjsDENIED
Reading a plugin's skills still worksread plugins/* · ✓
Strict also blocks
git fetch · git pull · git cloneNETWORK
dig · nslookupDNS
socat · openssl s_client · lynxSOCKETS
Local git, tests and builds still rungit commit · npm test · ✓
Polish

Smaller things you'll notice.

A few clicks that should have worked already.
Now a step card on a live run opens that step's live log, each terminal tab has its own close button, and Ask Worca sits in a round button in the corner instead of a bar over your work.

click a step, see its logclose a terminal from its tabHaiku 5.5 in the model listdiffs show only the run's own commits
The terminal pane after git status, with the tab's close button pressed: Close this terminal? A command has run, closing it ends the shell

A terminal that ran a command asks before it closes.

Where to click now
A step card on a live run→ its live log
× on a terminal tab→ closes that shell
The round button, bottom right→ Ask Worca · ⌘K
Model list→ Haiku 5.5

A step that never ran stays plain: there is no log to open yet.

And the receipts

Shipped, tested, verified live.

8,309
Tests green0 failing · +15.5k test lines
+26.6k
Lines landed364 files · 37 commits on dev
24
PRs mergedsince v1.9.0 · 2 days
13
Network commands closedunder Strict · git fetch · dig · socat
The round Ask Worca button with its tooltip
Ask Worca, out of the waya round button · name and ⌘K on hover
✓
Mock stays mockacross a pause and resume · no key for script-only runs
WORCA · changelog · v1.9.0 → v1.10.0 Oct 7 – Oct 8, 2026