From checkout to a working agent.
The Stable Quickstart below covers both macOS and Windows. The activation page remains the source of truth for your private key, prepared installer, and Private MCP URL.
Get SIDRA OS and open your private setup
Start from the subscription page. After payment, SIDRA opens the activation surface that prepares your permanent Activation Key and the installer command for your computer.
Get SIDRA OSInstall the Stable runtime
Use the prepared command shown on your activation page. If you need the public Stable bootstrap again, choose your platform:
curl -fsSL https://install.sidra-ai.com/macos/install.sh | /bin/bashirm https://install.sidra-ai.com/windows/install.ps1 | iexLet SIDRA prepare its Brain
SIDRA Brain is local, Markdown-backed project memory. It prepares the shared context layer automatically; Obsidian is optional visualization, not a setup requirement.
Enable native Computer Control
Computer Control uses CuaDriver as a separate prerequisite. SIDRA recognizes it dynamically when it becomes ready.
/bin/bash -c "$(curl -fsSL https://install.sidra-ai.com/macos/setup-cua.sh)"irm https://install.sidra-ai.com/windows/setup-cua.ps1 | iexThe platform helper installs the pinned driver and verifies Computer Control readiness. SIDRA detects the ready driver without requiring a normal runtime restart.
Connect the real Chrome profile
Enable the SIDRA Chrome extension during onboarding. Browser Control attaches to your normal Google Chrome profile and opens ordinary tabs there — it does not create a separate isolated browser.
Connect your AI client
After activation, copy the Private MCP URL from the setup page. Add a connector named SIDRA OS in a supported AI client, paste the URL, and use No Authentication for that private connector.
Use SIDRA to get the current workspace.Add WhatsApp now or later
Onboarding gives you a simple Connect / Skip choice. If you skip it, you do not need to reinstall SIDRA later — pair WhatsApp from Terminal whenever you want Owner Control.
One topic per page. Same order everywhere.
Use the focused command guides below instead of scanning one long terminal reference. The order here matches the SIDRA COMMANDS menu in the sidebar.
Files, terminal, apps — one execution layer.
SIDRA gives the connected AI a consistent way to inspect, change, run, and verify work on the actual machine instead of stopping at instructions.
Workspace
The canonical project context. Switching workspace tells SIDRA which project, paths, Brain context, and execution scope the agent should operate inside.
- Select and validate the real project
- Keep execution context scoped to the right work
- Bound projects restore Brain + HANDOFF automatically
File System
Work directly with project files instead of asking you to copy content into chat. SIDRA keeps protected credentials and sensitive runtime state outside the model’s reach.
- List, read, search, patch, write and move
- Create directories and soft-delete safely
- Atomic writes with backups
Execute
Build, test, run local servers, use installed toolchains, and manage background or interactive processes through SIDRA’s internal execution path.
- Use the signed-in user’s real PATH and SDKs
- Run commands or manage long-lived processes
- Poll, wait, send input, stop and inspect outcomes
Computer Control
Drive desktop applications when the job cannot be completed through files or command-line tools alone. SIDRA uses the native computer-control path and verifies effects before retrying.
- Inspect visible UI before acting
- Target stable UI elements before coordinates
- Control normal app and system UI
SIDRA Brain is shared memory for real projects.
Instead of re-explaining a project in every new chat, SIDRA supplies bounded current context to connected agents and keeps durable project knowledge in user-owned Markdown.
The latest canonical state, not an uncontrolled dump of past chats.
The exact objective and continuation point travel between supported agents.
Important choices, proven fixes, tasks, and reusable knowledge stay with the project.
A different supported AI client can continue from the same project context.
Work in the Chrome you already use.
Browser Control operates through the SIDRA extension inside the user’s real Google Chrome profile, so web work can stay connected to the same authenticated environment.
Navigate. Read. Type. Click. Complete workflows.
SIDRA can open normal tabs, navigate, inspect pages, enter non-sensitive text, click controls, work with forms, and wait for real page state changes.
One conversation can coordinate other coding agents.
When you explicitly ask for delegation, SIDRA can discover supported authenticated coding agents, hand off bounded work, resume an exact session, or coordinate a multi-lane fleet with scoped writers and final verification.
Bounded background implementation or review with explicit scope, preserved owner changes, and verification expectations.
Open and continue a real interactive provider session when you want a visible discussion with that agent.
Reach SIDRA from WhatsApp.
The optional paired channel can receive verified Owner Control events, resolve contacts, send and reply to messages, and wake the SIDRA workflow while preserving local owner identity.
SIDRA shapes how the work gets done.
Runtime-native skills add structured planning, minimal engineering, visual intelligence, reference research, and quality discipline without forcing the same heavyweight workflow on every task.
Structured specification and implementation when the task actually needs it.
Prefer the smallest correct change, reuse what exists, and avoid unnecessary architecture.
Design intelligence for product structure, responsive behavior, hierarchy, and usability.
Craft and quality review that protects visual consistency and interaction detail.
Measured reference research when you provide a real website or visual target.
Debugging, TDD, complexity review, and computer-use behavior activate when relevant.
Doing the action is not enough. SIDRA checks the outcome.
SIDRA’s unified verification path can inspect runtime identity, artifact hashes, customer packages, and release parity. Other tools also return effect evidence so the connected AI can distinguish an intended action from a confirmed result.
Ask for the outcome, not the tool sequence.
A normal SIDRA request can move through project context, files, code, terminal, browser or desktop, tests, verification, and Brain continuity without turning you into the operator between every step.