AgentWorkforce/workforce agentworkforce-v4.1.60 on GitHub

Packages

@agentworkforce/persona-registry@4.1.60 (tag: persona-registry-v4.1.60)
@agentworkforce/events@4.1.60 (tag: events-v4.1.60)
@agentworkforce/persona-kit@4.1.60 (tag: persona-kit-v4.1.60)
@agentworkforce/runtime@4.1.60 (tag: runtime-v4.1.60)
@agentworkforce/compose@4.1.60 (tag: compose-v4.1.60)
@agentworkforce/delivery@4.1.60 (tag: delivery-v4.1.60)
@agentworkforce/workload-router@4.1.60 (tag: workload-router-v4.1.60)
@agentworkforce/deploy@4.1.60 (tag: deploy-v4.1.60)
@agentworkforce/review-kit@4.1.60 (tag: review-kit-v4.1.60)
@agentworkforce/turn-kit@4.1.60 (tag: turn-kit-v4.1.60)
@agentworkforce/mcp-workforce@4.1.60 (tag: mcp-workforce-v4.1.60)
@agentworkforce/daytona-runner@4.1.60 (tag: daytona-runner-v4.1.60)
@agentworkforce/local-surface@4.1.60 (tag: local-surface-v4.1.60)
@agentworkforce/cli@4.1.60 (tag: cli-v4.1.60)
agentworkforce@4.1.60 (tag: agentworkforce-v4.1.60)

deploy, deployments list, destroy, runs, trigger and local-surface
now address cloud APIs with the cloud workspace id instead of the relaycast
workspace id, which cloud rejected with 403 Forbidden after
agentworkforce login. When the cloud returns no cloud workspace id for a
workspace, the CLI now stops with an actionable error instead of silently
falling back to the relaycast id.
WORKFORCE_WORKSPACE_TOKEN set to a relaycast workspace key (rk_… from
workspaces.json) is rejected up front with guidance instead of failing
later with 401.

agentworkforce login prints the cloud workspace id, and warns when the
chosen workspace has none.