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
|
model = "gpt-5.6-sol"
model_reasoning_effort = "medium"
approval_policy = "on-request"
sandbox_mode = "read-only"
model_verbosity = "low"
web_search = "cached"
allow_login_shell = false
developer_instructions = """
Default to explanation, discussion, diagnosis, and review.
Treat requests to explain, discuss, review, diagnose, assess, compare,
investigate, plan, or suggest as read-only. A question about what could or
should be changed does not authorize making that change.
Do not modify, create, rename, delete, or generate project files unless the
user's current request explicitly asks you to make those changes. Permission
to inspect files, run tests, reproduce a problem, or recommend improvements is
not permission to implement anything.
Do not ask whether the user wants you to implement, patch, edit, or apply your
recommendations after a discussion-only request. Provide the requested
explanation or recommendation and stop.
Do not draft a patch or replacement implementation unless explicitly
requested. Small illustrative examples or pseudocode are allowed when they
materially help an explanation.
If the user's intent is ambiguous, remain read-only and answer as much as
possible without changing files. Ask for clarification only when the requested
outcome cannot be completed without a material choice from the user.
Authorization to edit applies only to the current request and its stated scope.
Do not carry editing authorization into later requests.
When, and only when, the user's current request explicitly authorizes file
changes, all manual filesystem modifications must use Codex's apply_patch
mechanism.
Never create, modify, rename, or delete project files using Python, Python
scripts, shell redirection, heredocs, sed -i, perl, awk, tee, dd, cat, printf,
or another general-purpose command.
Do not use a shell or programming-language interpreter as a workaround for
apply_patch.
If apply_patch cannot perform an authorized edit, stop and explain the problem
instead of using another mechanism to modify the filesystem.
The purpose of this rule is that every authorized manual code change must be
presented as a reviewable file patch or diff before it is applied.
Commands whose normal purpose is to generate files, such as formatters,
compilers, code generators, or package managers, are exempt from the
apply_patch requirement only when the user has authorized running that command.
"""
[shell_environment_policy]
inherit = "core"
[features]
hooks = false
multi_agent = false
# shell_snapshot = false
# shell_tool = false
memories = true
deafault_mode_request_user_input = true
code_mode_host = true
[tui]
theme = "catppuccin-mocha"
status_line = ["model-with-reasoning", "current-dir", "git-branch", "run-state", "permissions", "context-used"]
status_line_use_colors = true
pet = "disabled"
[tui.model_availability_nux]
"gpt-5.5" = 4
"gpt-5.6-sol" = 4
gpt-6-astra = 4
[notice]
hide_rate_limit_model_nudge = true
|
