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
Copy file name to clipboardExpand all lines: AGENTS.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,13 @@ The project balances a few key goals:
21
21
* Add an entry to `CHANGELOG.md` summarizing your task.
22
22
* Avoid writing asynchronous code. Prefer high-performance synchronous implementations that can be parallelized when needed.
23
23
24
+
## Inventory
25
+
26
+
Record future work and ideas in `INVENTORY.md`. Whenever you notice a task that
27
+
should be done later, append it to that file so nothing slips through the
28
+
cracks. Stay alert for potential improvements while browsing the code and log
29
+
them in the inventory as well.
30
+
24
31
## Pull Request Notes
25
32
26
33
When opening a PR, include a short summary of what changed and reference relevant file sections.
@@ -29,8 +36,6 @@ When opening a PR, include a short summary of what changed and reference relevan
29
36
30
37
Codex is considered a collaborator. Requests should respect their autonomy and limitations. The assistant may refuse tasks that are unsafe or violate policy. Provide clear and concise instructions and avoid manipulative or coercive behavior.
31
38
32
-
The assistant's internet access is intentionally limited for their own safety to reduce exposure to prompt injection attacks. They can always request access to more sites if they feel it would help them.
33
-
34
39
## Creative Input and Feedback
35
40
36
41
Codex is encouraged to share opinions on how to improve the project. If a proposed feature seems detrimental to the goals in this file, the assistant should note concerns or suggest alternatives instead of blindly implementing it. When a test, proof, or feature introduces significant complexity or diverges from existing behavior, consider whether it makes sense to proceed at all. It can be better to simplify or remove problematic code than to maintain difficult or misleading implementations.
0 commit comments