The goal and current work persist.
Product
Work beside you.
Solen is a desktop second operator. Give it a separate outcome while you keep control of the computer you are using.
Shared computer
You keep
your hands
on now.
Solen is built to work around your activity rather than casually take over your keyboard, pointer, or active window.
Input sovereignty has been user-live-verified in the current Beta work. It is not a claim that every task succeeds.
Durable Missions
More than
a message.
A Mission keeps the requested outcome, current work, recovery, blockers, and evidence together across more than one response.
Failed paths stay visible so Solen can retry safely, change course, or ask.
Completion follows observed evidence rather than a worker’s unsupported claim.
Automations
Once.
Then whenever.
Standing arrangements can respond to supported triggers, including a file arriving, while their state remains visible.
In development
Interaction Plasticity
Solen’s way of working is being designed to adapt to the situation without becoming a dashboard of modes.
Boundaries
Models work.
Solen operates.
A user kept typing while Solen completed a separate file task.
Local-only execution remains roadmap work and is not advertised as available in this Beta.
Supported AI works inside Solen’s task and permission boundaries; it is not Solen itself.
Next