# ctask Status Line Setup

## Claude Code Integration

ctask includes helper scripts that display task context in Claude Code's status line.

### Prerequisites

Run `scripts/install.ps1` (or `just install`) first. This places the helper scripts at:

- Windows: `%LOCALAPPDATA%\ctask\bin\ctask-statusline.sh`
- Unix: copy `scripts/ctask-statusline.sh` to `~/.local/bin/`

### Setup

Add the following to your `~/.claude/settings.json`:

**Windows (after install):**

```json
{
  "statusLine": {
    "type": "command",
    "command": "bash /c/Users/<you>/AppData/Local/ctask/bin/ctask-statusline.sh"
  }
}
```

Replace `<you>` with your Windows username.

**Linux / macOS:**

```json
{
  "statusLine": {
    "type": "command",
    "command": "bash ~/.local/bin/ctask-statusline.sh"
  }
}
```

### Verify

Run `ctask doctor` to check that the status line is configured correctly.

### Output

When inside a ctask session:

```
(ctask:arch-notes|local) ~/ai-workspaces/general/2026-04-05_arch-notes
```

When NOT in a ctask session: no output (falls through gracefully).

### How It Works

The scripts read only from environment variables set by ctask:

- `CTASK_TASK` -- task slug
- `CTASK_MODE` -- execution mode (local/container)
- `CTASK_WORKSPACE` -- full workspace path

No file parsing or subprocess calls are performed.

## Non-Claude Agents

For agents that do not support a dedicated status line, ctask provides an ephemeral
shell prompt prefix in `--shell` mode:

```
(ctask:arch-notes|local) user@host:~/path$
```

This is set via `PS1` (Unix) or `PROMPT` (Windows) and does not modify permanent
shell configuration.