Your work home on any machine.
The team's, the same for everyone.
Skills, personas, protocols and your agents' rules follow you from one computer to another. On a team, the lead defines the protocols and everyone inherits them — and work done with agents starts being measured.
Build your combination.
Who you are, where your work home lives, and who you work with are independent choices. Only one combination doesn't exist: a team requires an account.
It's the default mode: everything on disk, no account. From the first run the app already has a local id, so becoming an account later is attaching — not migrating.
Without an account there's nowhere for the home to travel. Choose account to sync.
A client's machine, a borrowed laptop, an environment where you don't want to keep anything. You sign in, work, and the configuration doesn't leave here.
Install Stellar on another machine, sign in, and your providers, skills and protocols arrive. The keys you type again — they don't travel.
You join the shared queue and inherit the lead's protocols, but your personal configuration stays only on this machine.
The same user, now inside a team. A user can belong to teams; the team isn't a separate account.
The home travels. The credential doesn't.
- provider declarations you wrote
- skills, personas, protocols and rules
- the names of the credentials the home uses
- ports, sockets, caches and processes
- the app catalog, which comes from the binary itself
- a path outside your home — reported on arrival, not faked
Stellar doesn't carry secrets. Your keys stay in each machine's keychain and you type them again when you arrive. The package only says the name of what will be missing.
It's not another kanban.
Queue, sprint, roles and verdicts already exist in the app. What's missing for a team is knowing who each person is and letting more than one write at the same time.
Switching machines and already being set up: skills, protocols and personas come along. What already goes through git, like AGENTS.md and CLAUDE.md, keeps going through git.
Today each dev has an artisanal configuration and nobody knows what the other set up. On Team, the group's protocols are a single one.
How many rounds until approval, which model delivers with fewer back-and-forths, where the average hides the median. Stellar already keeps that history; Team shows the group's.
The door is the last thing to be built.
Each stage delivers something on its own. Login comes after the home it leads to exists.
- ✓Who wrote each thingDONEEvery write in the Queue carries its author — the foundation for assigning work to a person.
- ✓Inventory of the work homeDONEThe map of what's yours, what's the machine's and what's the app's.
- ✓Local statisticsDONERounds until approval, cycle, cost — value proven with no server at all.
- ✓Real local identityDONEA person id and a machine id from the first run, so the account is just an attachment.
- ✓Secrets policyDONEDecided: the credential doesn't travel. The package carries the name, never the value.
- ◐Provider config syncIN PROGRESSFormat and path remapping done; transport is missing.
- 7Synced boardLATERHistory syncs on its own; the canvas needs a conflict strategy.
- 8Server, login and teamLATERThe door, lastly.
Want to know when it opens?
Each roadmap stage ships in a release. Watch the repository on GitHub (Watch → Releases) and you'll know when the account and Team arrive.