The best way to control Claude Code, Codex and more from any computer or phone

main
md 34 lines 1.44 KB
Rendered Raw
1 <!--
2 Read CONTRIBUTING.md before opening a PR. Review capacity is limited, and meeting
3 the requirements does not guarantee review or merging. Solve one underlying problem.
4 The same requirements apply to drafts. Draft status does not defer triage or closure.
5 Use a conventional commit title in plain language, such as "fix(web): new threads no longer spike CPU".
6 -->
7
8 ## Problem
9
10 <!-- Explain the problem in a sentence or two. Include expected behavior and
11 reproduction steps or environment where relevant. -->
12
13 ## Change
14
15 <!-- Explain how this fixes the problem. If it spans components or clients,
16 explain why those changes are needed for the same fix. Split independent fixes. -->
17
18 ## Scope
19
20 <!-- We accept bug fixes, not features. Link the issue that shows the bug. For a
21 small fix of an obvious bug, say why it needs no issue. If a maintainer asked for
22 this PR, link the request. -->
23
24 ## Verification
25
26 <!-- Describe the focused tests or manual checks you ran and the observed results
27 for the changed behavior. State anything you could not check. "Tests pass" alone
28 is insufficient; broad repo-wide checks are not required.
29
30 For UI changes, include clear before/after screenshots. Include a short recording
31 when motion, timing, transitions, or interaction details are needed to demonstrate
32 the change. Upload evidence to GitHub and embed or link it here. Never commit PR-only assets. -->
33
34 <!-- If you used an agent, end with the model and harness that did the work. -->