Add Gitea integration for Telegram work mode

README.md

@@ -13,6 +13,7 @@ only keeps connection-management commands.
 /whoami
 /repo <path-under-workspace-root>
 /ask <prompt>
+/work <prompt>
 /new
 /status
 /settings
@@ -34,6 +35,9 @@ only keeps connection-management commands.
 ```
 
 `ALLOW_PLAIN_TEXT=true` makes regular Telegram messages behave like `/ask`.
+Use `/work <prompt>` for write-capable tasks such as editing files, committing,
+pushing, or opening pull requests. Plain text and `/ask` stay read-oriented by
+default.
 
 `/settings`, `/models`, `/schedules`, `/records`, and `/sessions` return inline
 buttons, so you can change speed/model/reasoning settings, delete schedules,
@@ -93,6 +97,32 @@ The bridge scheduler runs inside the Telegram bot process. When a schedule is
 due, it calls Codex app-server and sends the result back to the stored Telegram
 chat id.
 
+## Gitea integration
+
+Set these optional values in `.env` to let Codex manage Gitea repositories,
+issues, pull requests, and HTTPS git authentication from Telegram:
+
+```env
+GITEA_BASE_URL=https://gitea.example.com
+GITEA_USERNAME=your-gitea-user
+GITEA_EMAIL=you@example.com
+GITEA_TOKEN=your-personal-access-token
+GITEA_DEFAULT_OWNER=your-gitea-user-or-org
+GITEA_DEFAULT_REPO=your-default-repo
+GITEA_GIT_AUTH_ENABLED=true
+```
+
+Codex receives Gitea MCP tools for repository, issue, branch, and pull-request
+metadata. The container also configures `GIT_ASKPASS` so HTTPS `git clone`,
+`fetch`, and `push` can use the token without embedding it in command lines.
+
+Example Telegram workflow:
+
+```text
+/repo nas_connection
+/work 이슈 #3을 확인하고 코드 수정 후 테스트해. 변경사항을 codex/gitea-tools 브랜치로 커밋하고 push한 뒤 PR을 열어줘.
+```
+
 ## Deployment
 
 1. Copy `.env.example` to `.env`.