Quickstart

This guide uses the hosted service. To run everything on your own machines instead, start with Self-hosting; the steps after that are the same.

1. Create a workspace and a project

Sign up with email, GitHub or Google. Your first workspace is ready to use.

In the console, choose New project. Pick a template (C++, Python, Java or TypeScript), set its parameters, preview the files and create the project. Names use letters, digits, ., _ and -. Agents pass the workspace and project names in every tool call.

2. Add your software client

Open Account settings → Software clients and add your software installation, for example Claude Code · Laptop. Choose its workspace scope and expiry, then copy the token and MCP settings from the setup dialog. The token starts with sk_ followed by 64 hexadecimal characters and is shown once. Create a separate entry for each installation so you can revoke it individually.

3. Connect your agent

Add the gateway's MCP endpoint to your agent with the token as a bearer token. For Claude Code:

claude mcp add --transport http gateway https://<your-gateway>/mcp \
  --header "Authorization: Bearer sk_…"

Other clients are covered in Connect your software. The project's Overview page in the console shows the exact URL and the workspace and project names to use.

4. Read and edit

Ask your agent to look around and make a change. A file-level edit first locks ::, then calls the file tool:

{
    "name": "worldline",
    "arguments": {
        "workspace": "acme",
        "project": "app",
        "action": "lock",
        "scopes": ["::"]
    }
}

{
    "name": "edit",
    "arguments": {
        "workspace": "acme",
        "project": "app",
        "path": "src/main.cpp",
        "old_string": "Hello, world!",
        "new_string": "Hello, Fughetta!",
        "operation_id": "first-edit"
    }
}

With an operation_id, sending the same call again returns the recorded result instead of editing twice; use the worldline tool's receipt action with worldline: "main" to recover it after a lost reply. Files you don't want listed or searched belong in Settings → Ignored paths.

The project's Insights tab and the workspace's Usage tab count the agent's tool calls and errors per day. See MCP tools for every tool.