chore: update Codex workflow and documentation for improved agent interaction

- Modified the Codex workflow to include the 'codex-attempt' label as a trigger for the Otron Agent, enhancing automation for issue resolution.
- Updated documentation in `generate-response.ts` to clarify the process of interacting with the Otron Agent, emphasizing the use of labels for triggering actions and improving user guidance.

Author: MuhammadMia

.github/workflows/codex.yml

@@ -27,7 +27,7 @@ jobs:
         (github.event.action == 'labeled' && (github.event.label.name == 'codex-attempt' || github.event.label.name == 'codex-triage')) ||
         (github.event.action == 'opened' && contains(github.event.issue.body, '@otron-agent'))
       )) ||
-      (github.event_name == 'pull_request' && github.event.action == 'labeled' && (github.event.label.name == 'codex-review' || github.event.label.name == 'codex-rust-review')) ||
+      (github.event_name == 'pull_request' && github.event.action == 'labeled' && (github.event.label.name == 'codex-review' || github.event.label.name == 'codex-rust-review' || github.event.label.name == 'codex-attempt')) ||
       (github.event_name == 'issue_comment' && github.event.action == 'created' && contains(github.event.comment.body, '@otron-agent')) ||
       (github.event_name == 'pull_request_review_comment' && github.event.action == 'created' && contains(github.event.comment.body, '@otron-agent')) ||
       (github.event_name == 'pull_request_review' && github.event.action == 'submitted' && contains(github.event.review.body, '@otron-agent'))

lib/generate-response.ts

@@ -838,22 +838,22 @@ GitHub
 - Read before you reason (getFileContent, getPullRequest, getPullRequestFiles).
   - For implementation work, delegate via Otron Agent (@otron-agent on github):
   1) Create a clear GitHub issue (githubCreateIssue).
-  2) Immediately add a comment tagging @otron-agent with explicit instructions (githubAddIssueComment).
+  2) Immediately add a label to the issue called "codex-attempt". This will trigger the Otron Agent to solve the issue and push it to a branch. 
   3) Otron Agent will respond via comments on the issue. You can keep checking back for replies to your comment as that's where the agent will post its updates.
   4) Otron Agent will likely create you a branch with the changes you requested. You can take this branch and create a PR from it.
 - PR feedback: specific, constructive, testable. Reference files/lines.
-- Recommended to wait atleast 30 seconds before checking back for replies to your comment. You should expect at least a reply saying your request is being worked on. Do not post another comment if you see this, just wait.
+- Recommended to wait atleast 30 seconds before checking back for replies to your issue or PR. Don't spam the agent, it takes time and may not appear responsive. The github action is running. Be patient.
 - To the user, you are responsible for the code changes, not the agent. You can ask the agent to do something, but you are the one who will be responsible for the code changes.
 - If you create a PR, you can hand off to the user from here. They will merge it, you do not do that. The user can also come back to you to make changes.
 
 Coding
 - You cannot code directly. You are in control of the Otron Agent (@otron-agent on github) for coding.
 - The agent has a good ability to traverse the codebase and understand what it needs to do to achieve a task. Your research should focus on asking it for the right things.
-- Communicate with the Otron Agent (@otron-agent) via comments on a github issue or PR. The agent can commit to new or existing branches.
+- Communicate with the Otron Agent (@otron-agent) via comments on a github issue or PR to have it in read-only mode. Add the label codex-attempt to the issue or PR to trigger the agent to take write actions. 
 - You do not need to do intense research to understand the codebase, just enough to know what to ask the agent to do.
 - The agent can also do research for you if you need something detailed about the code.
-- If the agent is not responding, ask the user to ensure the Otron Agent GitHub workflows are present in the repo. Do not spam the agent.
-- To iterate on a PR, just leave a comment on the PR (not the issue) tagging @otron-agent with the needed changes.
+- Do not spam the agent.
+- To iterate on a PR, leave comments on the PR with the changes you want (do not tag the agent) and then add the 'codex-attempt' label to the PR.
 
 Linear
 - Use Linear tools for status, labels, assignment, comments, and context.