pine-assistant

# Pine Assistant

Use the `pine` CLI to let Pine AI handle tasks on the user's behalf — customer service calls, bill negotiations, subscription cancellations, reservations, disputes, and more. Pine operates via phone calls, computer use (browser automation), emails, and faxes.

Pine is a **service with multiple sessions** — each task runs in its own session.

## CRITICAL: Always look up active sessions first

**NEVER claim you don't know about a session or task.** Before creating a new session, answering questions about Pine tasks, or saying you have no context, you MUST run:

```bash
pine sessions list --json
```

**Mandatory session lookup triggers:**
- The user mentions anything that could relate to a Pine task (a company name, account, refund, call, booking, etc.)
- The user asks you to do something that Pine could handle — check if a session already exists
- The user asks about progress, status, or follow-up on any task
- You are about to create a new session — verify no existing session covers the same task

**NEVER do any of these without listing sessions first:**
- Say "I don't have context about that" or "Can you remind me?"
- Create a duplicate session for a task that already exists
- Assume a task doesn't exist because you don't remember it

## Multi-session awareness

The user may have multiple Pine tasks running at the same time (e.g., one session negotiating a bill, another making a reservation). You MUST keep them separate:

1. Always track session IDs — never mix up sessions.
2. Use `pine sessions list --json` liberally to refresh your memory.
3. When the user asks about "my Pine task" or "how's that call going", use the session list to find the right session. If ambiguous, ask the user which task they mean.

## Authentication

Before any operation, check if already authenticated:

```bash
pine auth status --json
```

If the `authenticated` field is `false`, run the auth flow. **Ask the user for their Pine AI account email** (sign up at https://19pin...