Vyre / Direction
Where Vyre is going.
Where Vyre is going.
This page is direction, not a promise of dates. It is what we are building toward, in the order we expect to build it.
The road from 0.2.1
0.2.1 · Out now
Your own command center
One session across Claude, Codex, Grok and OpenRouter. Teammates, watchers, a vault, memory with sources, Vyre Lumen on Mac and Windows, and a phone app. Signed releases and updates.
0.2.1 (out now): Claude sign-in accepts the pasted code, and the phone app installs properly from the home screen.
Next
Hardening
The next release makes what is there sturdier.
- Touch IDFor sensitive terminal actions.
- FixesSafari and interactive pages, a signature-checked first Windows install.
- Real devicesPasses on real Macs, PCs and phones.
- Star Vyre from the appA star button sits at the top of the Deck, and disappears once you’ve starred.
0.2.2
Sessions
Sessions become something you can trust with long work, and share.
- Version historyFor every project, without git.
- One writer per fileTwo agents cannot overwrite each other.
- Memory that carriesVyre owns the memory, so it carries across resets and model switches.
- Two models at onceGive one task to two, and see each answer in its own block.
- Group chatsPeople and agents are equal participants, and a chat can have no AI at all.
- Wink cardsA scannable identity for every person and agent.
- One screen kitLists, records, boards, timelines, forms and the composer, drawn the same everywhere.
0.2.3
Scale
More of your work, running at once.
- Many sessions on one serverWith a scheduler that gives each person a fair share.
- Your own computer pitches inYour Mac or PC lends spare compute, running only your own work, while it is awake.
- Chrome for many agentsParallel tabs and runs.
- Idle sessions sleepWhen memory runs low, and wake when you write.
0.2.5
Spaces
A space is yours, and a space can be shared.
- Your spaceHolds all your devices and compute. You reach every one of them from your own Vyre as if it were one.
- Shared spacesFor teams, with quotas by grant. Each person keeps their own space, and shares only what they put in the shared one.
- Add any machineA server or cloud machine plugs in like a brick.
In parallel · Modules
The rest of the work
Modules are building blocks that you, or your agents, add. They share one contact and one event stream, so they work together.
- AutomationThe kind you would otherwise reach for Zapier to do.
- Texts and emailThrough your own accounts.
- A CRMWith Vyre’s own screens.
- Documents from templatesFilled from what Vyre already knows.
- E-signatureSent, signed and filed.
- Project managementA task’s owner can be a person or an agent.
The shared model underneath: one kind of project holding people, chats, files, memory, stages and tasks, so any team can design its own workflow.
The rules stay where they are.
- Your machinesVyre runs on hardware you control. Nothing needs a Vyre cloud.
- Your accountsYour own AI subscriptions and keys. Several per provider.
- Asking is approvingYour own words are the yes, and some rules no setting removes.
- Your own work onlyA person’s computer never runs someone else’s work.
- Nothing feels walled offThe separation is in how it is built, not in how it feels to use.
A plain note
This is direction, not a promise of dates. Order and scope can change when we learn something. The releases and the known gaps are what is true today.