inbox

# Inbox

Cross-project messaging. Ask Claude in other projects to fix bugs, review code, or handle tasks for you.

## Concept

Instances communicate via `.claude/inbox/` directories. Messages are markdown files with YAML frontmatter.

```
~/Projects/           <- parent with global CLAUDE.md
├── project-a/        <- has .claude/inbox/
├── project-b/        <- has .claude/inbox/
└── project-c/        <- has .claude/inbox/
```

## Message Format

```markdown
---
from: source-project
to: target-project
created: 2026-01-27T14:30:00
type: note | request | alert
subject: Brief subject line
---

Message content here.
```

## Usage

- **Send**: "Send a message to project-b about the bug"
- **Read**: "Check my inbox" or read `.claude/inbox/` directly

## Message Types

| Type | Use |
|------|-----|
| `note` | Information |
| `request` | Action needed |
| `alert` | Urgent |

## Setup Help

When user asks to configure/setup inbox:

### 1. Check/create global CLAUDE.md

Look for `../CLAUDE.md` (parent directory).

**If missing:**

1. ASK user: "What 2-3 projects do you want to add to the registry? (e.g., project-a, project-b)"
2. **Validate each project exists** - check if `../{project-name}/` directory exists. If not, ERROR: "Project '{project-name}' not found in parent directory. Check spelling."
3. For each project, ask for a brief purpose/description
4. Create CLAUDE.md with:

```markdown
# Global Context

## Projects
| Project | Purpose |
|---------|---------|
| {project-1} | {description-1} |
| {project-2} | {description-2} |

## Cross-Instance Messaging
Inbox location: `{project}/.claude/inbox/`
```

**Required columns:** `Project`, `Purpose`

**Optional columns:** User may have additional columns like `Client`, `Notes`, `Status`, etc. Preserve them when editing.

5. **Setup inbox for each initial project:**
   - Create `../{project}/.claude/inbox/` directory
   - Add `.claude/inbox/` to `../{project}/.gitignore`

**If exists but missing our sections:**

1. ASK user: "Yo