---
title: "Combie Quick Start"
description: "Connect your engineering stack and run your first investigation."
---
## Install

```bash
curl -fsSL https://combie.dev/install | sh
```

## Initialize

```bash
combie init
```

This creates `.combie/combie.db` and the credentials file in your project or home directory.

## Connect providers

Start with GitHub using your existing `gh` CLI auth:

```bash
combie connect github --use-gh
```

Add Vercel from environment variables:

```bash
combie connect vercel --use-env
```

Other providers require API tokens — see the [Combie quickstart on GitHub](https://github.com/BoringInfraCo/combie/blob/main/docs/public/QUICKSTART.md) for per-provider setup.

## Sync

```bash
combie sync
```

This pulls resources and builds proven relationships between them.

## Investigate a resource

```bash
combie investigate vercel:project:prj_abc123 --task dependency-impact --json
```

Task profiles:

| Task | Returns |
|------|---------|
| `change-review` | What changed + evidence chronology |
| `dependency-impact` | Proven connectivity and paths |
| `response-recall` | Prior investigations, resolutions, incidents |

## Set up agents

Expose read-only context to coding agents:

```bash
combie agent setup
combie mcp
```

Optional skill install:

```bash
npx skills add BoringInfraCo/combie --skill combie -a cursor -a claude-code -a codex
```

## Next steps

- [Use Cases](/docs/products/combie/use-cases)
- [MCP documentation](https://github.com/BoringInfraCo/combie/blob/main/docs/public/MCP.md)