> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Claude Cowork

> Install Deepline in Cowork and verify the session workspace before a provider-backed request.

[Human guide: work with your agent →](https://deepline.com/docs/human/claude-cowork.md)

Connect Deepline to a Cowork session and verify the workspace before a data
request. Your first win is a working, authorized CLI in the session's folder.

## Before you start

Use a Cowork account and a project folder that the session can access. Keep the
folder consistent across setup and later CLI calls. Allow the network access
required by your organization's policy.

Anthropic documents [plugin installation](https://support.claude.com/en/articles/13837440-use-plugins-in-claude)
and [Cowork access controls](https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork).
Client screens and organization controls can vary.

## 1. Add the Deepline plugin

Open Cowork's plugin customization flow. Add the Deepline marketplace:

```text theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
https://github.com/getaero-io/deepline-plugins
```

Install `deepline`. Open a session with the intended working folder.
Let an in-progress installation finish before starting another setup.

## 2. Authorize the workspace

Ask Cowork to follow the canonical installation instructions:

```text theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
Follow https://code.deepline.com/INSTALL.md in this session's working folder.
Complete CLI setup and report the effective workspace. Do not execute provider
lookups or write to a connected system yet.
```

Complete any browser authorization for the intended workspace.
Then ask Cowork to run:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline --version
deepline auth status --json
```

> [!TIP]
>
> The CLI starts, and authorization identifies the intended workspace. A plugin
> appearing in the library is not sufficient proof of CLI authorization.

## 3. Try a bounded request after setup

The following starter can perform provider-backed work and incur usage.
Review its plan and unresolved results before requesting more rows.

```text theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
/deepline-gtm Find 3 AI companies funded in the last 30 days, with founder contacts and verified work emails.
```

If the session cannot reach Deepline, inspect the effective network policy.
Ask the organization owner for required access when controls are locked.
Do not assume a local browser connection proves the session can reach it.

For repeated authorization, check the working folder and
[folder binding](https://deepline.com/docs/sdk-v2/multi-org.md). For CLI failures, use `deepline doctor --json`.
Ask Cowork to explain the failed check before repeating setup.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.