Using Tilebox CLI

Use this skill whenever interacting with the tilebox command-line tool. Prefer machine-readable output and command schema discovery so automation remains robust.

Core Rules For Agents

• Always ensure the CLI is up to date before relying on workflow behavior: check tilebox --version, follow Updating The CLI below, then refresh command schemas. Do not treat these skills as evidence that an older binary supports a new flag.
• Always pass --json in agent workflows when the command supports it; never pass --interactive.
• Always submit workflow-project jobs with --workflow . or an exact remote reference, including local managed-runner tests. Only use unscoped jobs for an explicitly requested direct Python runner or a Python script executed as a direct runner for testing; see tilebox-workflow-jobs.
• Use tilebox agent-context <command path> --output-schema before relying on a command's output shape.
• Pass authentication via TILEBOX_API_KEY unless the user explicitly asks to use --api-key.
• Use --api-url only when targeting a non-default API environment.
• For paginated commands, read next_cursor from JSON output and pass it back as --cursor until it is empty.
• Use tilebox agent-context <command> when behavior is unclear.

Authentication And API URL

The CLI authenticates with either: