Connect your computer

Everything so far happens between your phone and Kyra’s servers. This page adds a third place: your own machine. Once connected, Kyra can open files in your editor, type at your cursor, and see and steer the coding-agent sessions you have running — without your code ever leaving the machine.

You only need this if you want computer control. Notes, memory, and conversation all work without it.

Note

Computer control rolls out per account. If Kyra says it is not switched on for you yet, there is nothing to install until it is.

Requirements

• Node.js 22.6 or newer.
• Linux, macOS, or Windows with WSL. See Windows below — it is not an afterthought, it is the supported path.

Install

Four commands, on the machine you actually work on.

curl -fsSL https://dl.kyra-hi.com/install.sh | sh
kyra login
kyra init
cd ~/code/my-project && kyra connect

Command	What it does
install.sh	Installs the kyra command. If it needs root to write to your global npm directory it stops and asks you to re-run it with sudo sh — it never escalates by itself.
kyra login	Prints a short code and a link. Open the link, check the code matches, and this machine is approved against your account.
kyra init	Installs a small skill into your coding agent so a session can tell Kyra “I’m blocked” or “I’m done”. Use --codex for Codex instead of Claude Code.
kyra connect	Holds the connection open. Leave it running while you work.

Then ask Kyra: “What’s running on my machine?”

Important

kyra connect takes its writable root from the directory you start it in. Sessions Kyra starts can read more widely, but they only write inside that directory. Start it in your project root. To change it, stop the daemon and start it somewhere else, or pass --workdir <dir>.

Prefer not to pipe a script into a shell

curl -fsSL https://dl.kyra-hi.com/cli -o kyra-cli.tgz
npm install -g kyra-cli.tgz

Let Kyra drive your editor

The steps above let Kyra see sessions it starts. To reach the editor itself — opening files, searching your workspace, typing where your cursor is — install the VS Code extension.

Run these in the editor’s own terminal:

curl -fsSL "https://dl.kyra-hi.com/vscode" -o kyra-vscode.vsix
code --install-extension kyra-vscode.vsix
kyra install vscode

The first two install the extension. kyra install vscode switches on mediation, which additionally lets Kyra drive the Claude Code sessions running inside that editor.

Important

Reopen your Claude Code sessions afterwards. Mediation applies when a session starts, so anything already open stays unmediated until you reopen it. That is also how you undo it: kyra uninstall vscode, reopen, and nothing is in the path.

Note

Driving sessions is Linux and WSL only. It identifies who is connecting using a kernel credential that only exists there, so on macOS kyra install vscode refuses rather than writing a setting that would look applied and do nothing. The rest of the extension — files, search, typing — works on macOS.

If code is not a command, run Shell Command: Install ‘code’ command in PATH from VS Code’s command palette.

Reinstalling the .vsix is how you upgrade. The extension does not update itself.

Windows

Run everything above inside a WSL distribution, and attach VS Code to that WSL remote (Connect to WSL; the title bar then shows [WSL: <distro>]).

This is deliberate, not a gap. Kyra’s local door depends on two operating-system guarantees that Windows does not provide and — worse — does not report as missing, so it refuses to open there rather than appear secure while not being. The detail is here.

Check it worked

kyra version

• Prints a version and a build stamp. Quote both if you report a problem.
• VS Code’s status bar shows a Kyra item when the extension is attached.
• Ask Kyra “what’s running on my machine?”.

Keeping it up to date

kyra update            # install the latest published build
kyra update --check    # say what is available, install nothing

An update is a re-install of the same package, so it needs whatever rights the first install did — if npm’s global directory needs root, it says so and stops rather than escalating.

Two things to do afterwards: restart any running kyra connect, which keeps serving the build it started with until you do, and run kyra init again to refresh the agent skill.

Every option →

Turning it off

• Stop kyra connect (Ctrl-C) — control stops immediately.
• Revoke the machine from Settings → Coding agents in the portal — an instant kill-switch that does not require access to the machine.

Next

• What Kyra can do on your machine
• Driving coding agents by voice
• How much Kyra asks before acting
• Full CLI reference