Desktop is not a wrapper around the VS Code extension. It is a native runner surface over the same backend services: the shared Gateway, agent orchestration, model routing, approvals, billing, and real-time messaging.
What Desktop Owns
Desktop owns the local runtime experience for the workspace you open inside the app:
| Area | Desktop responsibility | | ---- | ---------------------- | | Session | Starts and tracks Desktop-owned agent sessions | | Workspace | Uses the folder selected in Desktop as the execution root | | Tools | Runs supported file, terminal, git, search, and browser-preview tools locally | | Approvals | Shows approval cards for actions that need human confirmation | | Results | Streams tool output and agent responses into the Desktop timeline | | Mobile handoff | Lets mobile monitor and approve the same backend-routed work |
VS Code remains the best surface for editor-native actions. Desktop is the full-screen standalone surface for people who want the agent loop without depending on an IDE extension.
Supported Desktop Tools
Desktop standalone currently supports the core local tools needed for agent work:
| Category | Examples |
| -------- | -------- |
| Files | read_file, create_file, update_file, delete_file, copy_file, move_file |
| Directories | list_files, create_directory, delete_directory |
| Search and edit | search_in_files, search_replace, insert_at_line |
| Terminal | execute_command, run_terminal_command, run_command |
| Git | git_status, git_diff, git_add, git_commit, git_pull, git_push |
| Browser preview | Browser tools when the Desktop browser runtime is available |
Unsupported tools fail closed with a clear message instead of silently falling back to another runner.
Workspace Context
The selected Desktop workspace is the local boundary for tool execution. File paths and command working directories are resolved inside that workspace.
This matters for three reasons:
- The agent can reason about the same project you selected in Desktop.
- Local file operations cannot intentionally target arbitrary paths outside the workspace.
- Mobile approvals stay tied to the Desktop session and workspace that requested them.
Session Isolation
Desktop sessions are isolated from VS Code sessions. A conversation started in Desktop belongs to Desktop; a conversation started in VS Code belongs to VS Code.
Both can use the same account and the same Gateway, but they do not secretly depend on each other. Cross-surface coordination happens through backend contracts and explicit device/session routing.
Typical Workflow
- Open MiraBridge Desktop.
- Sign in.
- Open a workspace folder.
- Ask the agent to inspect, plan, implement, test, or review.
- Approve file, terminal, git, or browser actions when they appear.
- Watch live command output and patch progress in Desktop.
- Use mobile to monitor or approve when you step away.
Recommended Prompts
For exploration:
Inspect this workspace and explain the app architecture. Do not edit files yet.For implementation:
Add the missing empty state to the billing usage page, then run the focused tests.For review:
Review my current git diff for bugs, security risks, and missing tests.Next Steps
- Terminal Commands - command execution details
- Approvals & Security - safety model and approval behavior