You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -14,127 +14,30 @@ Use your github-triage tool to triage issues.
14
14
15
15
This file is the source of truth for ownership/routing rules.
16
16
17
-
## Labels
17
+
Assign issues by choosing the team with the strongest overlap. The github-triage tool will assign a random member from that team.
18
18
19
-
### windows
19
+
Do not add labels to issues. Only assign an owner.
20
20
21
-
Use for any issue that mentions Windows (the OS). Be sure they are saying that they are on Windows.
21
+
When calling github-triage, pass one of these team values: tui, desktop_web, core, inference, windows.
22
22
23
-
- Use if they mention WSL too
23
+
## Teams
24
24
25
-
#### perf
25
+
###TUI
26
26
27
-
Performance-related issues:
27
+
Terminal UI issues, including rendering, keybindings, scrolling, terminal compatibility, SSH behavior, crashes in the TUI, and low-level TUI performance.
28
28
29
-
- Slow performance
30
-
- High RAM usage
31
-
- High CPU usage
29
+
### Desktop / Web
32
30
33
-
**Only** add if it's likely a RAM or CPU issue. **Do not** add for LLM slowness.
31
+
Desktop application and browser-based app issues, including `opencode web`, desktop-specific UI behavior, packaging, and web view problems.
34
32
35
-
#### desktop
33
+
###Core
36
34
37
-
Desktop app issues:
35
+
Core opencode server and harness issues, including sqlite, snapshots, memory, API behavior, agent context construction, tool execution, provider integrations, model behavior, documentation, and larger architectural features.
38
36
39
-
-`opencode web` command
40
-
- The desktop app itself
37
+
### Inference
41
38
42
-
**Only** add if it's specifically about the Desktop application or `opencode web` view. **Do not** add for terminal, TUI, or general opencode issues.
39
+
OpenCode Zen, OpenCode Go, and billing issues.
43
40
44
-
#### nix
41
+
###Windows
45
42
46
-
**Only** add if the issue explicitly mentions nix.
47
-
48
-
If the issue does not mention nix, do not add nix.
49
-
50
-
If the issue mentions nix, assign to `rekram1-node`.
51
-
52
-
#### zen
53
-
54
-
**Only** add if the issue mentions "zen" or "opencode zen" or "opencode black".
55
-
56
-
If the issue doesn't have "zen" or "opencode black" in it then don't add zen label
57
-
58
-
#### core
59
-
60
-
Use for core server issues in `packages/opencode/`, excluding `packages/opencode/src/cli/cmd/tui/`.
61
-
62
-
Examples:
63
-
64
-
- LSP server behavior
65
-
- Harness behavior (agent + tools)
66
-
- Feature requests for server behavior
67
-
- Agent context construction
68
-
- API endpoints
69
-
- Provider integration issues
70
-
- New, broken, or poor-quality models
71
-
72
-
#### acp
73
-
74
-
If the issue mentions acp support, assign acp label.
75
-
76
-
#### docs
77
-
78
-
Add if the issue requests better documentation or docs updates.
79
-
80
-
#### opentui
81
-
82
-
TUI issues potentially caused by our underlying TUI library:
83
-
84
-
- Keybindings not working
85
-
- Scroll speed issues (too fast/slow/laggy)
86
-
- Screen flickering
87
-
- Crashes with opentui in the log
88
-
89
-
**Do not** add for general TUI bugs.
90
-
91
-
When assigning to people here are the following rules:
92
-
93
-
Desktop / Web:
94
-
Use for desktop-labeled issues only.
95
-
96
-
- adamdotdevin
97
-
- iamdavidhill
98
-
- Brendonovich
99
-
- nexxeln
100
-
101
-
Zen:
102
-
ONLY assign if the issue will have the "zen" label.
103
-
104
-
- fwang
105
-
- MrMushrooooom
106
-
107
-
TUI (`packages/opencode/src/cli/cmd/tui/...`):
108
-
109
-
- thdxr for TUI UX/UI product decisions and interaction flow
110
-
- kommander for OpenTUI engine issues: rendering artifacts, keybind handling, terminal compatibility, SSH behavior, and low-level perf bottlenecks
111
-
- rekram1-node for TUI bugs that are not clearly OpenTUI engine issues
- thdxr for sqlite/snapshot/memory bugs and larger architectural core features
116
-
- jlongster for opencode server + API feature work (tool currently remaps jlongster -> thdxr until assignable)
117
-
- rekram1-node for harness issues, provider issues, and other bug-squashing
118
-
119
-
For core bugs that do not clearly map, either thdxr or rekram1-node is acceptable.
120
-
121
-
Docs:
122
-
123
-
- R44VC0RP
124
-
125
-
Windows:
126
-
127
-
- Hona (assign any issue that mentions Windows or is likely Windows-specific)
128
-
129
-
Determinism rules:
130
-
131
-
- If title + body does not contain "zen", do not add the "zen" label
132
-
- If "nix" label is added but title + body does not mention nix/nixos, the tool will drop "nix"
133
-
- If title + body mentions nix/nixos, assign to `rekram1-node`
134
-
- If "desktop" label is added, the tool will override assignee and randomly pick one Desktop / Web owner
135
-
136
-
In all other cases, choose the team/section with the most overlap with the issue and assign a member from that team at random.
137
-
138
-
ACP:
139
-
140
-
- rekram1-node (assign any acp issues to rekram1-node)
43
+
Windows-specific issues, including native Windows behavior, WSL interactions, path handling, shell compatibility, and installation or runtime problems that only happen on Windows.
0 commit comments