parley-cli 0.2.0

Terminal-first review tool for AI-generated code changes
Documentation 
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
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114

# MCP Integration

Parley exposes an MCP-compatible JSON-RPC interface over stdio.

## Transport

- Supports both `Content-Length` framed and newline-delimited JSON-RPC messages.
- Implements `initialize`, `tools/list`, `tools/call`, `resources/list`, and `resources/read`.
- Advertises embedded documentation through MCP resources with `parley://docs/{slug}` URIs.

## Typical tools

- `list_reviews`
- `get_review`
- `list_open_comments`
- `add_reply`
- `mark_comment_addressed`
- `mark_comment_open`
- `set_review_state`
- `run_ai_session`
- `get_documentation`

## Embedded documentation

Agents can discover Parley's built-in markdown docs through `resources/list` and read any page with `resources/read`.

Available resource URIs:

- `parley://docs/keybindings`
- `parley://docs/overview`
- `parley://docs/quickstart`
- `parley://docs/review-workflow`
- `parley://docs/mcp`

Agents that prefer tools can call `get_documentation`.

Inputs:

- `doc`: optional doc slug, title, source path, or URI. If omitted, the tool returns the available docs list.

## `run_ai_session` behavior

Inputs:

- `provider`: `codex` | `claude` | `opencode`
- `mode`: `reply` | `refactor` (optional; defaults by API call site)
- `comment_ids`: optional explicit thread IDs

Global gate:

- review-wide AI selects threads by thread status; explicit comment IDs target those comments directly

Target filtering:

- `mode=refactor`:
  - auto-target (`comment_ids` omitted): only `open` threads
  - explicit `comment_ids`: still only `open` threads are processed
- `mode=reply`:
  - auto-target (`comment_ids` omitted): `open` and `pending`
  - explicit `comment_ids`: status filter is bypassed for selection, so `addressed` can be processed

After processing:

- AI response is added as a thread reply
- thread status typically becomes `pending` (different-author reply path)

## Example calls

Reply mode over all eligible threads:

```json
{
  "name": "run_ai_session",
  "arguments": {
    "review_name": "my-review",
    "provider": "codex",
    "mode": "reply"
  }
}
```

Refactor mode over unresolved threads:

```json
{
  "name": "run_ai_session",
  "arguments": {
    "review_name": "my-review",
    "provider": "codex",
    "mode": "refactor"
  }
}
```

Reply mode on explicit thread IDs:

```json
{
  "name": "run_ai_session",
  "arguments": {
    "review_name": "my-review",
    "provider": "codex",
    "mode": "reply",
    "comment_ids": [12, 18]
  }
}
```

## Notes

- Tools that operate on review state require an explicit `review_name`.
- Thread state updates are explicit tool calls.
- `set_review_state` accepts Parley review states (`open`, `under_review`).
- `run_ai_session` supports `reply` and `refactor` modes.