01 · Active development
Now
The build in front of us: the parts of ORION that have to work before anyone can use it seriously.
- In progress
Visual context engineORION
Reading the active window, selection, and task history you permit, and turning it into a short-lived picture of the work.
- In progress
Permission-aware action layerORION
Per-capability permissions, one visible step at a time, and a stop control that always takes effect.
- In progress
Multi-provider routing foundationORION
Matching each step of a request to a model by capability, latency, privacy requirement, and cost.
- In design
Readable activity recordORION
A plain-language history of what ran and why, exportable and deletable by you.
02 · After the core loop is dependable
Next
Work we intend to do once the core loop holds up in daily use. Sequenced, not scheduled.
- Planned
Private early-access buildORION
A limited build for people on the early-access list, with direct feedback channels instead of a public launch.
- In design
Keyboard and voice workflowsORION
Complete parity between visual, keyboard, and voice paths, tested with assistive technology rather than approximated.
- In design
Granular privacy controlsORION
Marking content as device-only, with routing that refuses to send it anywhere else.
- Planned
Documentation and changelogiMpact
Public documentation and a changelog that records what shipped, what broke, and what we withdrew.
03 · Direction, not commitment
Later
Genuine intentions with unresolved questions. Any of these can be dropped if the answer turns out to be no.
- Exploring
On-device model routingLabs
How far daily work can be carried by smaller local models before quality falls off. Currently internal research.
- Exploring
Personal workflow memoryLabs
Long-term memory of how you work, without turning the product into surveillance. Unsolved, honestly.
- Exploring
Developer extension interfaceORION
A safe way for others to add tools to ORION, which requires the permission model to be settled first.
- Planned
Paid plans and accountsiMpact
Accounts, billing, and the tiers published on the pricing page. Nothing is billable until ORION is generally available.
- Exploring
A second productLabs
Deliberately unnamed. It appears here when it is real enough to describe without invention.
كيف ننشر هذه الصفحة
ثلاث قواعد لهذه الصفحة.
- No dates we cannot keep
- We publish order and state instead of quarters. A date we would have to walk back is worse than no date.
- Nothing listed as done until it is
- Items move to shipped only when a person outside the team can use them. Design targets stay labelled as design targets.
- Removals are published too
- If we drop an item, it is recorded in the journal with the reason rather than quietly deleted.