Skills, MCP and tools

Skills

A skill is a named, reusable set of instructions, such as how to run your tests or how your deploy works. An agent loads it when the task calls for it.

Type / in the composer to list your skills alongside the agent's built-in commands. Skills install at global scope (available everywhere) or workspace scope, stored under <workspace>/.mirasim.

mirasim ui-cli --port 4970 skill list                       # workspace + global
mirasim ui-cli --port 4970 skill install --source https://github.com/o/r --scope global
mirasim ui-cli --port 4970 skill create --name run-our-tests --scope workspace
mirasim ui-cli --port 4970 skill update --name run-our-tests
mirasim ui-cli --port 4970 skill remove --name run-our-tests

MCP servers

Add an MCP server as a local command or a URL, with its own environment variables, and its tools become available alongside the built-ins. Servers use global or workspace scope. The list shows both the servers Mirasim manages and the ones an agent brought itself.

mirasim ui-cli --port 4970 mcp list
mirasim ui-cli --port 4970 mcp add --name gh \
  --command npx --arg -y --arg @some/mcp-server --scope global
mirasim ui-cli --port 4970 mcp toggle --name gh --enabled false
mirasim ui-cli --port 4970 mcp health --name gh     # live handshake probe

Connectors

Connectors are a curated catalog on top of MCP. Install one, give it its secrets or run it remotely, and enable it per agent. You can validate a connector against the live service and re-run its OAuth grant when a token expires.

mirasim ui-cli --port 4970 connectors list
mirasim ui-cli --port 4970 connectors install SOME_ID --mode remote --secret KEY=value
mirasim ui-cli --port 4970 connectors enable SOME_ID --agent claude
mirasim ui-cli --port 4970 connectors validate SOME_ID    # records tool count / error
mirasim ui-cli --port 4970 connectors auth SOME_ID        # (re)start OAuth, prints the URL
mirasim ui-cli --port 4970 connectors search "issue tracker"   # the official registry

Connector search also queries the official MCP registry.

The CLI tools already on your computer

Mirasim lists the common developer CLIs on your PATH, such as git, gh and docker, and shows whether each is signed in.

mirasim ui-cli --port 4970 cli-tools    # dev CLIs on PATH + auth state
mirasim ui-cli --port 4970 clis         # agent CLIs: version / latest / update available

Computer Use

Computer Use is a tool called by the agent in your current session. Calls follow that session, including its model and account.

Open Settings → Computer Use and turn it on; it is off by default. Enable the connections you want the agent to use, then describe the task in your session, such as checking a page or filling in a form.

Browser connections

The three connections can be enabled together. Each keeps its own browser state and logins; copying logins affects only the independent browser. The agent selects a connection for each call.

macOS apps

Enable macOS apps and open Manage to check permissions. Accessibility is required to read controls and operate apps; Screen Recording is needed for screenshots and live preview. Follow the panel to grant them in macOS System Settings, then return to Mirasim to recheck.

When the agent operates an app outside your always-allowed list, the session asks for permission, and allowing it covers the current task only. To stop being asked about an app, add it under Settings → Computer Use → Always-allowed apps; you can remove it there later.

Electron apps

Computer Use can also operate Electron apps that expose a renderer debugging endpoint. Start the target app with its debugging port enabled and give the endpoint to the session's agent.

Live preview

Turn on Live preview to watch the browser or app the agent is operating. The preview is read-only. Closing it hides the picture while the session keeps working; stop the task with the separate stop control or stop the session's turn.

mirasim ui-cli --port 4970 computer-use
mirasim ui-cli --port 4970 config set computerUse.guiAgentEnabled=true