change gnupg ssh agent, to openssh ssh agent, update codex config for newest version, update nvim

1 files changed, 41 insertions, 13 deletions

diff --git a/codex/config.toml b/codex/config.toml
index ff7a423..5968e92 100644
--- a/codex/config.toml
+++ b/codex/config.toml
@@ -1,31 +1,59 @@
-model = "gpt-5.6-terra"
+model = "gpt-5.6-sol"
 model_reasoning_effort = "medium"
 
-approval_request = "on-request"
+approval_policy = "on-request"
 sandbox_mode = "read-only"
 model_verbosity = "low"
 web_search = "cached"
 allow_login_shell = false
 
 developer_instructions = """
-All manual filesystem modifications must use Codex's apply_patch mechanism.
+Default to explanation, discussion, diagnosis, and review.
 
-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.
+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 a requested edit, stop and explain the problem
+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 manual code change must be presented as
-a reviewable file patch/diff before it is applied.
+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 purpose is to generate files as their normal operation, such as
-formatters, compilers, code generators, or package managers, are exempt when
-the user has authorized running that command.
+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]
@@ -37,7 +65,7 @@ multi_agent = false
 # shell_snapshot = false
 # shell_tool = false
 memories = true
-deafult_mode_request_user_input = true
+deafault_mode_request_user_input = true
 code_mode_host = true
 
 [tui]