Skip to main content
Human guide: work with your agent → Set up Deepline in the Bot’s execution environment, then verify its effective workspace. A working browser session on your laptop does not prove that the Bot’s terminal has Deepline authorization.

Before you start

Open a Bot conversation with terminal access and an appropriate working folder. Use the same folder for setup and later requests. See Grok Bot’s architecture for its computer model and skills for saving a proven process.

1. Ask the Bot to install Deepline

The installation guide chooses the supported global or project-local path. Do not force a global installation when the environment cannot support one.

2. Verify the environment

Complete the requested browser authorization. Ask the Bot to run:
The CLI runs in the Bot’s environment and identifies the intended workspace. Preserve the working folder for later requests.
If setup fails, use deepline doctor --json. Follow the returned next action. A pending authorization is not a reason to start several setup flows.

3. Review one request before repeating it

This starter can execute provider work and incur usage:
Review identity, source evidence, unresolved rows, and actual usage. Save the run ID before expanding the request. Save a repeatable skill only after its pilot meets the acceptance rule. Ask the Bot to explain a failed check before changing the method. For file-based work, use Batch CSV enrichment.