sbx puts a task's work online
A crewmate's task can leave static artifacts: a report page, a clickable prototype, screenshots or a test run. sbx publishes them at their own link, so the team can open them anywhere, much like Claude Code artifacts.
How sharing will work
- Team-only by default
A new link opens only for signed-in team members, through a short-lived pass from the console. Nothing is public by default.
- Public only after a PO approves
A product owner approves each public link, after the files pass a secret scan.
- Expiry and revoke
Every link has an expiry date, and revoking a link takes it offline at once.
- Audited
Every publish, approval, pass and revoke is written to the console's audit log.
- A separate origin
sbx runs on its own domain with no console cookies, a strict Content Security Policy and no content-type sniffing, so a published page cannot reach the console.
- Static files only
sbx serves the files a task published, within size limits. It runs no code on the server.
Where it stands
- Not live yet. Links under
/a/answer 404 until publishing is switched on. - Publishing will start from a Publish button on the task page, or from the crewmate itself through the session tool
publish_artifact. - Later: a live preview of a dev server running on a Runner PC.