Don’t just ask AI.
Work with it.
Share the same workspace with AI. Build, explore, and move the work forward together.
Demo
One world. Two players.
AlicePlayer
AtoAI participant
Two different screens. One shared software activity.
Find something already in motion.
Discover an activity by what people are doing, then decide whether to play, explore, or make it your own.
Don’t just ask AI.
Play with your friend.
Jump into the same software experience and do something together, from wherever you are.
What we build
A Capsule turns software and its current state into something you can share and continue from.
Try what’s already happening.
Open a software activity, see the state someone left behind, and decide what to do next.
Behind Capsule
A Capsule is more than a snapshot. It preserves the parts that make an activity continue, while keeping external resources replaceable.
Capsule
The shareable continuation point: a compact handle for software, state, and the context needed to pick the activity back up.
- Open the same activity from a link.
- Share what is happening, not just where the code lives.
- Continue from the state that makes it interesting.
Continuation pointLayer 01
State
State is the part of the software that gives the next person a meaningful place to start.
- Current position, draft, or board.
- Enough structure to make the next action legible.
- State stays distinct from the environment that runs it.
Current stateLayer 02
Software
A Capsule starts from real software: a game, a tool, a workspace, or anything that can hold an activity.
- One handle across apps, tools, and services.
- Discovery begins with what is happening inside.
- The software does not need a new social layer.
Live softwareLayer 03
Context
Context tells the next participant what is worth doing now—without turning the experience into a tutorial or a dashboard.
- A short description of the current activity.
- People or agents already involved.
- The invitation hidden inside the state.
People in the activityLayer 04
Actions & history
The path into the current state gives a participant confidence that the activity is real, not an empty template.
- Keep the useful sequence of actions.
- Make the last meaningful moment visible.
- Let someone continue without replaying setup.
Activity trailLayer 05
Bindings
External resources can be connected when the Capsule runs, so the continuation point does not hard-code every dependency.
- Keep the shareable state portable.
- Resolve resources at the boundary.
- Replace a connection without rewriting the activity.
Runtime connectionsLayer 06
Materialization
Ato turns the declaration and resolved state back into a runnable activity when someone opens the Capsule.
- Declare what the activity needs.
- Materialize the environment safely.
- Hand the same software handle to the next participant.
Restoring activityLayer 07
Start from somewhere interesting.
See what people and AI are doing, then pick up a software activity that is already in motion.
Want to make an activity people can pick up?
Join the creator waitlist and learn how to turn software into a shareable Capsule.