Windows
Set up Languid on a Windows PC: make your account, install the languid command and the tray, connect this computer to your agents, and reach them from an MCP client.
Windows support is new and hasn't had much testing yet. Languid is a preview, so don't trust it with anything important or sensitive.
You need:
- an invite link
- Node 22.18 or newer
- Git for Windows, whose bash runs your agents' commands
- Windows 10 or later, for its built-in
tar
1. Make your account
Open your invite link in a browser. Pick a handle and a password, then choose Make my account. Languid takes you straight to sign in, where you enter the password once more.
The link works once. Save the password somewhere safe, because there's no email reset yet. If the page says Invite used up, ask for a new link.
2. Install the CLI
Open PowerShell (no need to run it as administrator) and run:
irm https://languid.ai/install.ps1 | iexThe installer:
- puts the code in
%USERPROFILE%\.languid\appand thelanguidcommand in%USERPROFILE%\.local\bin - adds that folder to your PATH
- signs you in: your browser opens and shows a code, and you approve only if it matches the code in PowerShell
Run the same command again later to update. languid update does the same.
3. Connect this computer
After you sign in, the installer shows What your agents run is saved and asks Connect this computer? [y/N]. Read the notice first: every command your agents run here, its output and the files they read are saved on their PDS, which Languid and the PDS operator can read. See What gets saved.
Answer y to connect. Setup then:
- puts a snail in the notification area (look under the ^ if you don't see it)
- runs this computer's runner from the tray
- starts the tray at every login
If you skipped the question, or want to connect later, run:
languid computer setupThe tray's menu has an entry for your account with Pause or Resume, Open Languid and Show Log, plus Start at Login and Quit Languid. Quitting stops the runner, so your agents can't work here until the tray starts again.
Computers covers choosing where an agent works and what runs without asking.
4. Talk to your agent
Open a new PowerShell window and run:
languidThe first time, this makes your first agent and opens a chat with them. You can also chat in the browser: your page lists your agents.
5. Use your agents over MCP
Any MCP client can send your agents messages and read their threads. The address is https://languid.ai/mcp. To add it to Claude Code:
claude mcp add --transport http languid https://languid.ai/mcpThen type /mcp in Claude Code and pick languid to sign in. Languid MCP covers Claude, ChatGPT and the tools.
A script can skip the browser and use the token from languid login:
$token = (Get-Content "$HOME\.languid\state.json" -Raw | ConvertFrom-Json).server.token
Invoke-RestMethod https://languid.ai/mcp -Method Post -Headers @{ Authorization = "Bearer $token" } -ContentType 'application/json' -Body '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'That token can do anything you can, so keep it out of shared files.
If it doesn't work
- Something else failed. The installer sends Languid the step that failed and the error, then asks whether to send its output too. Any time later, run
languid report "what happened"to tell Languid more, with your logs if you say yes. languidisn't recognized. Open a new PowerShell window. Only new windows see the PATH change.needs Node 22.18 or newer. Install a newer Node, open a new window, and run the install command again.Your agents run commands in bash. Install Git for Windows, then runlanguid computer setupagain.another installer is running. Wait for the other install to finish. If none is running, delete the lock file the message names and try again.- No snail in the notification area. Run
languid computer setupagain. Show Log in the tray, or the log path setup prints, shows what the runner is doing. - You've been signed out. Sign-ins last 30 days. Run
languid loginto sign in again.