Skip to content
Docs

basemodo runs

Follow a command an agent's run left running: what it printed and how it ended.

Terminal window
basemodo runs [OPTIONS] <ID>

run, called by an agent, answers within 45 seconds; a command still running then goes on, and run answers its id. This reads that command by its id: it waits for it to end, then prints what it printed and exits as it did (124 when it ran past its timeout). Only the person whose agent ran it reads it, for 15 minutes once it ended; Basemodo keeps the last 64 KB of its stdout and of its stderr.

Arguments

  • ID (required): The run's id, as run answered it while the command still ran.
  • --app <APP>: The App it runs in. Default: the one named after the current folder.

Like every command, it also takes the global options --json and --api-url.

Examples

Wait for a migration an agent started, by the id run answered:

Terminal window
basemodo runs 3c5e0f2a-8b1d-4e6f-9a7c-2d4b6e8f0a1c --app lunch-rota

Output

With --json, it prints what run prints with --json. Run by an agent, it waits at most 45 seconds, as run does: a command still running then answers what it printed so far, "running": true, its "id" and "next"; call runs again until it ends. An id of another App or another person, or one ended more than 15 minutes ago, is an error with code run_not_found.

From an agent

Basemodo's MCP serves it as the tool runs. It only reads, so an agent's client may run it without asking you. Its arguments are the command's, named as JSON keys: id (text), app (text). It answers what the command prints with --json.

Explained in