Pick the integration path
The rule is simple: if the agent can run shell commands, it can run Deepline.
Use skills where the agent supports them. Use the plain CLI everywhere else.
Ask the agent to install Deepline
Give the agent this instruction:deepline@latest,
run deepline setup --json, handle the persistent project-local fallback in a
restricted sandbox, complete browser authorization, and verify CLI, skills,
auth, and workspace state.
For a direct terminal install:
deepline setup installs the hosted skill bundle for the detected agent and
keeps it current. The hosted installer supports Codex, Claude Code, Cursor,
Gemini CLI, and Antigravity. For an unknown agent it installs the bundle for all
supported targets. Hermes remains CLI-only.
OpenClaw uses the CLI or MCP and does not have a hosted Deepline skill target.
Give the agent a concrete job
Good agent instructions name the file, output file, run name, row range, and tool payload.Use the GTM agent repo
For repo-backed agent workflows, start from the Deepline GTM agent project:deepline-gtm-agent
Reference repo for improving Deepline GTM agent workflows across coding
agents.
Troubleshooting
The agent says deepline is not found
The agent says deepline is not found
Ask the agent to follow
https://code.deepline.com/SKILL.md in that
environment. It will use a persistent project-local install when sandbox
policy blocks a global installation.Setup or authentication failed
Setup or authentication failed
Read the failed phase and exact retry command from
deepline setup --json. If
setup reports a diagnostic command, run it. Otherwise use deepline doctor --json to inspect CLI, skills, auth, workspace, and API state.The agent invented a Deepline command
The agent invented a Deepline command
Stop and check the internal content canonicals before running it. For
enrichment, use the command shape on this page.