Choose the install path
Desktop and CLI have separate instructions. Check your operating system and chip; do not mix installation environments.
Choose your systemConnect a model to read files, edit code and run tools in your chosen workspace. Follow a clear path from installation to your first verified task.
Windows · macOS · LinuxSeparate Desktop and CLI guides
Check installation, model connectivity and task results separately.
Desktop and CLI have separate instructions. Check your operating system and chip; do not mix installation environments.
Choose your systemSave provider credentials in local settings and select an available model. Installers do not include model API credits.
Connect a modelUse a disposable workspace without secrets. List files first, verify the path, then permit changes only when intended.
Verify your first taskThe links below target Windows x64 and Apple Silicon. Review the download record and platform notes before running an installer.
Check Desktop versions and compatibility →Desktop, npx and global CLI prerequisites are explained separately.
Use the Windows x64 Desktop installer, or the PowerShell CLI section when needed.
Open installation guide →The linked DMG is for Apple Silicon; Intel Mac users can follow the CLI path.
Open installation guide →Prepare Node.js, start the local Web UI with npx, then verify the model and test folder.
Open installation guide →DSH brings models, sessions, workspaces, tool permissions and plugins into an executable workflow. When you choose a cloud model, requests are sent to its provider.
Check the workspace, approvals and actual results when reading files, editing code or running commands.
Read the DSH overview →Compare model choice, tool access and extensibility rather than a single leaderboard.
Compare agent workflows →Follow the exact error to check credentials, model configuration, ports or permissions.
Open the guide →Set up the provider first, then review pricing assumptions, retries and task acceptance.
Open the guide →Start with a working session, then check extension sources, installation paths and access boundaries.
Open the guide →Start with the exact message you see.
MISSING_CREDENTIALNo usable credential is saved for the provider.UNKNOWN_MODELThe selected model is not available under the configured provider.401 authentication failedThe provider rejected authentication for the request.EADDRINUSE / EACCES :3080The local port is occupied or reserved by the operating system.Select model / input disabledA provider, model or workspace still needs to be selected.npm.ps1 cannot be loadedPowerShell blocked the npm or npx script shim.Workspace permission deniedOperating-system or tool permissions blocked the file operation.Choose a test folder, configure the model, review approvals and inspect actual files.
Separate provider specifications, calculation assumptions and measured results.
Open the articles →Start with a small repair task and record the environment, tests and costs. These are templates, not unrun model rankings.
Open the task and template →Distinguish linked downloads from historical references; old records are not current checks.
Open version records →