Nine Point Labs
The Word from Ninepoint Labs

Speakeasy 0.3: Your bots can start the tasks now

· 2 min read

Speakeasy already kept coding agents in named, hidden terminals so you could see what was running without drowning in windows. As of 0.3, other programs can hand it work the same way you do from the bar.

An MCP server on stdio

speakeasy mcp speaks the Model Context Protocol over standard input and output. No network port, no daemon to babysit. Point Claude Code, Grok Bot, Hermes, or any other MCP client at the binary and it gets four tools:

  • list_agents — which agents are installed and visible, with models and effort levels
  • find_repo — where a GitHub repo is checked out on this machine
  • create_task — start a task with title, description, agent, and optional model, effort, and repo or folder
  • list_tasks — what is already running, so a bot does not start a duplicate

A bot watching your repos can pick Claude or Codex, write the brief, and park the job in the right local checkout. It shows up in your Speakeasy list like anything you started yourself. The client’s name is stored as the task’s origin, and Speakeasy leaves your new-task picker defaults alone.

Approvals stay yours

The MCP path deliberately cannot pass extra agent arguments, so a bot cannot flip permission prompts off. It also cannot peek at a task’s screen, type into it, or stop it. The agent still asks you before risky actions; you still answer.

find_repo strips credentials out of remote URLs before it reports them. Add the MCP server only to clients you trust, same as you would any tool that can start processes in your project folders.

Titles and prompts off the process list

0.3.1 closes a quieter hole. The Omarchy panel used to put the task title and description on the speakeasy new command line, where any other user on the machine could read them with ps. They now go over stdin as one line of JSON (--stdin-json). The CLI already avoided stuffing prompts into argv for normal use; the panel catches up.

Try it

speakeasy mcp
# or wire it into Claude Code:
claude mcp add speakeasy -- ~/.local/bin/speakeasy mcp

Upgrade with your usual Omarchy plugin path, or pull ninepointlabs/speakeasy and run ./install.sh. If your workflow is “bot finds the problem, I approve the fix,” Speakeasy is now the handoff.