---
title: "Combie Use Cases"
description: "Common workflows for engineering context and operational memory."
---
## Incident response

Compose context around a Vercel project — deployment history, related GitHub repo, Sentry issues — in one investigation:

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

## Change review

See what changed across providers for a resource before approving a deploy:

```bash
combie investigate github:repo:my-org/my-app --task change-review
```

## Dependency mapping

Trace proven paths from repo to deploy to domain to monitoring:

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

## Agent stack awareness

Give Cursor, Claude Code, or Codex deterministic engineering context via MCP:

```bash
combie agent setup
# In your agent config, Combie exposes 5 read-only MCP tools
```

## Operational memory

Record how your team responded and recall precedents on the next incident:

```bash
combie investigate vercel:project:prj_abc123
# Save investigation, record resolution, link incidents
combie investigate vercel:project:prj_abc123 --task response-recall
```

## Offline investigation

Read commands work without network after sync — useful for on-call without VPN:

```bash
combie sync  # while online
combie investigate vercel:project:prj_abc123  # works offline
```
