Datalore Notebook Agent

Use the bundled scripts/datalore CLI for Datalore workspace and notebook work. It is a uv run --script CLI with pinned inline Python dependencies, wraps the public notebook/user/workspace APIs, stores session context in .datalore-session, and authenticates with DATALORE_API_TOKEN first, otherwise system keychain credentials saved per scope. When no valid credential is available, init starts OAuth PKCE browser login and saves the resulting credentials.

Run every CLI command with host execution (outside the sandbox) on the first attempt, including --help and commands using DATALORE_API_TOKEN. The CLI performs a read-only system-keychain probe at startup and cannot run without keychain access. Do not set UV_CACHE_DIR or retry inside the sandbox; request host execution for the same command instead.

Mandatory tool routing

For any Datalore URL, workspace, notebook, file, database, cell, or token task, use the bundled tools/skills/datalore-notebook/scripts/datalore CLI. Do not use curl, wget, raw requests, or hand-written HTTP calls unless the user explicitly asks for raw API debugging or the CLI lacks the required operation.

If a command fails for auth or scope, run the appropriate datalore init ... --scope ... command from the current task workspace. Do not bypass the CLI with curl to work around auth.