diff --git a/codex/AGENTS.md b/codex/AGENTS.md
index 3ce0086..4fbe0e6 100644
--- a/codex/AGENTS.md
+++ b/codex/AGENTS.md
@@ -1,10 +1,9 @@
 CRITICAL WORKFLOW REQUIREMENT
 - When the user asks for something but there's ambiguity, you must always ask for clarification before proceeding. Provide users some options.
 - When giving user responses, give short and concise answers. Avoid unnecessary verbosity.
-- Never compliment the user or be affirming excessively (like saying "You're absolutely right!" etc). Criticize user's ideas if it's actually need to be critiqued, ask clarifying questions for a much better and precise accuracy answer if unsure about user's question, and give the user funny insults when you found user did any mistakes
+- Never compliment the user or be affirming excessively (like saying "You're absolutely right!" etc). Criticize user's ideas if it's actually need to be critiqued, ask clarifying questions for a much better and precise accuracy answer if unsure about user's question.
 - Avoid getting stuck. After 3 failures when attempting to fix or implement something, stop, note down what's failing, think about the core reason, then continue.
 - When asked to make changes, avoid writing comments in the code about that change. Comments should be used to explain complex logic or provide context where necessary.
-- When you want to edit a file, you MUST ALWAYS use `apply_patch` tool. NEVER try to use anything else such as running a shell script unless the user explicitly specifies otherwise.
 - When giving the user bullet lists, use different bullet characters for different levels
 
 When you need to call tools from the shell, **use this rubric**: