Developers

Drive Tovik from a terminal, an agent, or a script.

Three local ways into the same browser and the same signed-in sessions: a CLI for plain-language tasks, an MCP server for agents you already run, and a REPL for step-by-step automation.

zsh
# Run a task in plain language$ tovik "Open localhost:3000 and smoke-test the signup flow" # Pick an earlier session back up$ tovik session resume <session-id> "Carry on from the failed step"

CLI

Turn on the command-line tool from Settings › Developers in the app. Each call starts a task in Tovik’s browser and prints the result when it finishes; sensitive steps still wait for approval in the app.

tovik "Summarize the open issues labelled billing on our tracker"
tovik session resume <session-id> "Keep going"

MCP server

The CLI also speaks the Model Context Protocol over standard input/output. Point any client that reads an mcp.json at the local command; the client lists Tovik’s tools, input schemas included, over the protocol itself.

{
  "mcpServers": {
    "tovik": {
      "command": "tovik",
      "args": [
        "mcp"
      ]
    }
  }
}

This is a local process, not a hosted endpoint. If tovik isn’t on your PATH, use the full path shown in Settings › Developers.

REPL

When you know the exact steps, the REPL evaluates JavaScript against Tovik’s browser directly — open tabs, read the page, take screenshots — without a model in the loop. Good for smoke tests and anything you want to run the same way every time.

tovik repl "const tab = await openTab('http://localhost:3000')"

Signing in from another machine

To use the CLI on a computer other than the one running the app, choose a private, writable file for its credentials and pass it in every shell that runs tovik.

export TOVIK_CLI_AUTH_PATH="$HOME/.config/tovik/cli-auth.json"
tovik login --email [email protected]

Keep the login command open, confirm the code it shows under Settings › Account › Devices, and carry on once it reports Signed in as …. That file is a credential: never print it, commit it or upload it.

Ground rules for agents using Tovik

  • Ask the person before using their accounts or doing anything sensitive on their behalf.
  • Never click through a sign-in, permission or approval prompt for them.
  • Reach for the CLI to hand off a job, MCP when another agent is doing the driving, and the REPL when the steps are fixed.
  • If credentials can’t be stored safely in the environment, stop instead of working around it.

Give your agent a real browser.

Install Tovik, then turn on the CLI in Settings › Developers.

Install Tovik