rigmode 0.1.2

Attach work modes to AI coding agent prompts
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56

# Configuration

Zero-config default: load modes from `~/.config/rigmode/modes`.

## Config File

**Path:** `~/.config/rigmode/config.toml` (or `$XDG_CONFIG_HOME/rigmode/config.toml`)

Create this file when you want to customize modes dirs or gate markers.

```toml
modes_dirs = ["~/my/modes"]

[gate]
markers = ["wrong", "redo"]
```

`~/` is expanded. Earlier directories win on duplicate mode names. `--modes-dir` on the CLI overrides this list.

## Options

### `modes_dirs`

Directories to load `*.md` mode files from.

- **Type:** Array of paths
- **Default:** `["~/.config/rigmode/modes"]` (when unset / empty)

```toml
modes_dirs = ["~/my/modes", "./modes"]
```

### `[gate].markers`

Words that mark a prompt as a human intervention (a rejection of the agent's work). Matched on the prompt's **first line** with the same rules as mode triggers: case-insensitive, literal, ASCII-letter ends guarded so `no` stays out of `notification`. An empty list disables recording.

- **Type:** Array of strings
- **Default:** `[]`

```toml
[gate]
markers = ["wrong", "redo", "that's not it"]
```

See [Usage](usage.md#gate-recording) for when a record is written.

## Data Files

Under `~/.local/share/rigmode/` (or `$XDG_DATA_HOME/rigmode/`), one JSON object per line, written best-effort so `attach` always exits `0`:

| File | Contents | Browse with |
|------|----------|-------------|
| `attach.jsonl` | One line per attach | `rigmode log` |
| `gates.jsonl` | One line per intervention | `rigmode gate` |

Old-schema lines fail to parse and are skipped.