Map Gitea issue conversations to Codex execution in the synced local repository checkout.
IssueAgentManager now supports native Codex backend.issue_comment event:
owner/repo/issue_number/workspace/repos/<owner>/<repo>)codex exec with cwd in repository/workspace/repos/.autocoder/issue_sessions/...OPENAI_API_KEY + codex login --with-api-key)auth.json) via optional secret mountautocoder-codex-auth secret created from host Codex authCODEX_HOME on PVCcodex login status detection checks both stdout and stderr.codex login --device-auth.autocoder-codex-auth from current host ~/.codex/auth.json.AUTOCODER_CODEX_LOGIN_MODE=none and restarted deployment.Logged in using ChatGPT.default-deny-egress and only allowed DNS + in-cluster Gitea.allow-egress-https (TCP/443) in namespace autocoder-engine.https://api.openai.com/v1/models -> 401 (reachable)https://auth.openai.com/codex/device -> 302 (reachable)codex exec ... "Reply with exactly: it works" -> it works#18:
172173: it worksgitea-http.gitea.svc.cluster.local.AUTOCODER_CODEX_DISABLE_SANDBOX to issue-agent Codex invocation.AUTOCODER_CODEX_DISABLE_SANDBOX=true, issue-agent runs:
codex exec --dangerously-bypass-approvals-and-sandbox ...3319ff0.AUTOCODER_CODEX_DISABLE_SANDBOX=true.#18 validation comment id 187 requested networked git command.188 returned:
3319ff075fb4fd7b14a7c6c1495d3e0e0bcd4ebd refs/heads/main