What users control
- Users can review artifact visibility before sharing.
- Revision state and compare surfaces are visible.
- AI use remains explicit rather than hidden.
Core
How it works
Artifacts and Receipts
Keep useful outputs attached to the room, with reviewable state.
Artifacts turn work into durable outputs, while receipts help show what happened, what was reviewed, and how the output can be reused.
Ready
Artifact panel proof screenshots
How it works
Built for the current Early Access wedge.
Each page stays inside the proven product boundary: shared context, visible control, durable output, and a support path.
Create or receive a useful output during room work.
Open the artifact panel to review list, grid, or detail state.
Compare revisions, publish to the room, or use the artifact in AI when appropriate.
Product proof
Real screenshots, not mockups.
These proof images come from the running product and retained launch-readiness checks.
Current boundaries
- Artifacts do not imply every file type or workflow is already supported.
- Publishing or deleting important artifacts should stay deliberate.
- Customer or private data should not become public proof without authorization.
Request-led Early Access
Try Artifacts and Receipts in Early Access.
Start with the current feature surface, and use help if setup, access, or trust state is unclear.