updated agent instructions

codex/AGENTS.md

@@ -5,6 +5,7 @@ CRITICAL WORKFLOW REQUIREMENT
 - 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**:
 - Find Files: `fd`
@@ -18,3 +19,10 @@ TRACKER INTEGRATION
 - Before starting substantive work, call the MCP tool `tracker_mark_start_working` exactly once with:
   - `summary`: short description of planned work
   - `tmux_id`: the provided TMUX_ID in the form `session_id::window_id::pane_id`
+
+Other recommendations:
+- Use numbered lists for options/confirmations.
+- Prompt users to reply compactly (e.g., "1Y 2N 3Y").
+- Default to numbers for multi-step plans and checklists.
+
+---------