Built for real work.
A persistent computer. A team of agents. The context and controls to put them to work.
Restless is pre-release. These are implemented capabilities, not a promise that every hosted workflow is ready.
A computer of its own.
A Linux workspace that stays with the company, instead of disappearing with a chat.
Why the runtime matters- Browser, desktop, terminal.
- Browse, run commands, work with files, and inspect the result in a real desktop.
- Files that stay put.
- Keep projects, dependencies, Git worktrees, and local previews in the company workspace.
- Install the tools you need.
- Use Python for analysis, Node for a site, or Godot for a game. Add compatible packages as the work requires.
Tool installation depends on permissions, available resources, platform support, and licences.
A team that stays.
Keep roles, responsibility, and working context across attempts.
Why stable teams matter- One point of contact.
- The Exec coordinates the company. Accountable leads own outcomes and bring in specialists.
- Room to branch.
- Delegate distinct work, explore alternatives, and bring results back for review.
- Context with a source.
- Actor checkpoints preserve working memory with links to evidence—not a promise of perfect recall.
Keep the work moving.
The goal stays. Attempts can change.
Set the outcome.
Give the team a goal, context, and limits. Track ownership and dependencies as work branches.
Try. Check. Revise.
Keep failed attempts and useful findings attached to the work. Change the approach without losing the goal.
Review the result.
Open the artifact, inspect its evidence, and request changes. Schedule recurring work when it makes sense.
Your attention counts.
Decisions need context. Not another stream of agent chatter.
- Prepared handoffs.
- See what happened, what needs your judgement, and which work it affects.
- Scoped approvals.
- Review a specific request for authority. Follow the resulting continuation rather than guessing what happened next.
- Work can continue.
- An owner decision need not stop unrelated work. Attention and execution are separate concerns.
Still your company.
Make your standards reusable. Across people, agents, and the work they produce.
- Company truth.
- Keep facts, decisions, examples, and sources together. Separate what you know from what you assume.
- Your voice.
- Use approved and rejected examples to guide blogs, newsletters, emails, support replies, and product copy.
- Your visual language.
- Keep references and reusable visual patterns. Review the actual page or artifact against them.
- How you work.
- Make expectations for disagreement, uncertainty, customer recovery, and quality tradeoffs explicit.
Set the standard.
Choose the effort. Give the team a reference worth reaching.
Quality playbooks guide native testing, independent criticism, and revision. When an approach stalls, a clean reset can leave the failed solution behind.
These guide the work; they don’t guarantee an outcome. More effort can cost more without producing a better result.
Four effort levels.
- Fast
- Thorough
- Exceptional
- Frontier
- Start with a reference.
- Use company standards and strong examples to define what good looks like.
- Judge the actual work.
- Test the site, open the document, or run the software. A confident summary is not evidence.
Bring your tools.
Connect capabilities to the people and work that need them.
- Remote MCP & OAuth.
- Connect compatible tool servers, authorise access, and discover the tools they actually expose. Connections record their purpose and assigned actor.
- Models & agents.
- Use configured model providers and agent adapters. Attribute model spend to the company and its work.
- Infisical secrets.
- Use scoped secret references for credential custody. Provider credentials stay in the owner account plane; connected-tool OAuth uses its own scoped runtime material.
- Authority with a scope.
- Permissions and approvals bound supported external effects. They are not a blanket guarantee over every command an agent can run.
- Receipts, not guesswork.
- Inspect recorded effects, work evidence, and health signals. See the basis for a decision.
- Cost in view.
- Track attributed model spend and configured budget ceilings. Missing metering is not treated as free usage.
- An open core.
- Inspect, run, and adapt the Apache-2.0 Core locally. The hosted service and brand are separate.
Cloud, with clear limits.
Same company model. Hosted operation. A private rollout while the full experience is being qualified.
Cloud adds account entry, company selection, provisioning, and runtime management around Core. Rooms, membership, and native documents provide the foundations for working together.
- Verified in the private rollout
- Deployment, account entry, and owner sign-in.
- Implemented; hosted validation pending
- Full company work, collaborative documents and rooms, and continuity across restarts and phones.
- Deferred for this rollout
- Sharing with friends and publishing company outputs.
- Disabled in this rollout
- Automated backups. Restore readiness is not claimed.
Availability reviewed 17 September 2026. Core is pre-release; neither this page nor a healthy deployment is a production-readiness certification.
See for yourself.
Read the code, the architecture, and the reasoning behind it.
Sources behind these features
Claims were checked against Core revision 2f2fab1 and the private Cloud implementation. Source code shows what is implemented; it does not prove every hosted flow works end to end.