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

# Continue - open-source copilot with screen context

> Set up Screenpipe with Continue, the open-source AI Copilot for VS Code and JetBrains, so it can reference your screen history while you code.

[Continue](https://github.com/continuedev/continue) is an open-source AI coding assistant with 20k+ GitHub stars. It works in VS Code and JetBrains IDEs, and supports MCP servers for external context.

## Setup

### VS Code

1. Install Continue from the VS Code marketplace
2. Open Continue settings
3. Edit `~/.continue/config.json`:

```json theme={"system"}
{
  "mcpServers": [
    {
      "name": "screenpipe",
      "command": "npx",
      "args": ["-y", "screenpipe-mcp"]
    }
  ]
}
```

4. Restart VS Code

### JetBrains

1. Install Continue from JetBrains marketplace
2. Open Continue settings
3. Add the same MCP configuration
4. Restart the IDE

## Usage

Once configured, Continue can access your screen history:

```
> @screenpipe what was I working on this morning?

> find the error I saw in my terminal and help me fix it

> what documentation was I reading about react hooks?
```

## Example workflows

**Code with context:**

```
> I was looking at how another project handles authentication,
> find that code and help me implement something similar
```

**Recall errors:**

```
> there was a typescript error earlier about types,
> find it and explain how to fix it
```

**Meeting follow-up:**

```
> what did we discuss in the standup about the API changes?
> help me implement those changes
```

## Available tools

Via MCP, Continue gets access to:

| Tool | Description |
| - | - |
| `search-content` | Search screen text (accessibility-first, OCR fallback), audio transcriptions, and input |
| `activity-summary` | Lightweight overview of app usage, speakers, and recent texts for a time range |
| `search-elements` | Search structured UI elements from the accessibility tree |
| `frame-context` | Full accessibility tree, URLs, and text for a specific frame |
| `list-meetings` | List detected meetings with duration, app, and attendees |
| `export-video` | Export screen recordings as MP4 for a time range |

## Requirements

* Screenpipe running on localhost:3030
* Continue extension in VS Code or JetBrains
* Node.js >= 18.0.0

## Troubleshooting

**MCP server not appearing in Continue?**

1. Check Screenpipe is running:
   ```bash theme={"system"}
   curl http://localhost:3030/health
   ```
   you should see `{"status":"healthy"}`

2. Verify the config file location:
   * VS Code: `~/.continue/config.json` (check it exists and is valid JSON)
   * JetBrains: open Continue settings and confirm the MCP config is saved

3. Restart the IDE completely (not just the Continue extension)

4. If the server still doesn't appear, remove and re-add it in Continue settings

**Screenpipe queries returning empty?**

* Verify Screenpipe has data:
  ```bash theme={"system"}
  curl "http://localhost:3030/search?limit=1"
  ```
  if empty, Screenpipe hasn't recorded anything yet — let it run for a minute and try again

* Check screen recording permissions are granted (System Settings on macOS)

* Confirm you're querying a time range with recorded data

**"Error calling tool" in Continue?**

* Check the Screenpipe process is still running (it may have crashed):
  ```bash theme={"system"}
  curl http://localhost:3030/health
  ```

* Check Screenpipe logs:
  * macOS/Linux: `~/.screenpipe/screenpipe.log`
  * Windows: check event viewer or `%APPDATA%\screenpipe\logs`

* Restart Screenpipe if needed:
  ```bash theme={"system"}
  npx -y screenpipe@latest record
  ```

**VS Code extension not showing MCP tools?**

* Reload the Continue extension: use VS Code's Command Palette (Cmd+Shift+P) → "Reload Window"
* Verify `config.json` is valid JSON (check for trailing commas)
* Ensure Node.js >= 18.0.0: `node --version`

Still stuck? [join our Discord](https://discord.gg/screenpipe).


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