Make the session inspectable beyond its original operator
A hosted Claude Code workspace retains the conversation, job lifecycle, and outputs so a teammate can understand the work without needing access to the original terminal.
use case
Use Claude Code in a shared workspace when a team needs visibility and handoff.
Run Claude Code through a hosted project workspace when implementation work needs durable sessions, recoverable outputs, browser review, and a clear team boundary.
Keep project artifacts with the work that created them
Generated files and other outputs are attached to the run record, making review and follow-up less dependent on manually forwarding local files.
Continue after reloads and role changes
The browser workspace restores the durable project session and replayable activity so the next responsible developer has a stable starting point.
why this page exists
What teams need to understand.
Each page focuses on the actual workflow question: browser access, persistent sessions, durable jobs, artifacts, replay, runtime support, and team-scoped workspace custody.
Hosted Claude Code
Team-visible session history
Browser review
Recoverable artifacts
Durable project context
Replayable work record
Related guides
From runtime choice to the workflow.
FAQ
Direct answers for searchers.
Who should use a Claude Code team workspace?
Teams that already rely on Claude Code and need the work to remain visible, reviewable, and recoverable across developers and browser sessions.
Can the team inspect generated outputs later?
Yes. The hosted workspace keeps artifacts and run activity attached to the project-scoped session for later review and follow-up.