# Gitea for AI agents. Managed auth, ready-made tools.

> Browse repositories, manage issues and pull requests, and read files in Gitea on behalf of each of your users.

- Page: https://www.agent200.com/connectors/gitea/
- Category: Developer tools
- Authentication: Managed OAuth
- Identifier in code: `gitea`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-18

## Instructions for AI agents

Connector: Gitea, through Agent200. In code: "gitea".
What it does: Browse repositories, manage issues and pull requests, and read files in Gitea on behalf of each of your users.
Page: https://www.agent200.com/connectors/gitea/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Gitea's own page, through the authorization link Agent200 returns. Never ask a user for a Gitea password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: gitea_list_repos, gitea_get_file_contents, gitea_list_issues, gitea_list_pull_requests. Write tools: gitea_create_issue, gitea_create_issue_comment, gitea_create_pull_request. Name "gitea" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/gitea/framework/claude/
   https://www.agent200.com/connectors/gitea/framework/chatgpt/
   https://www.agent200.com/connectors/gitea/framework/claude-code/
   https://www.agent200.com/connectors/gitea/framework/muse/
   https://www.agent200.com/connectors/gitea/framework/grok-bot/
   https://www.agent200.com/connectors/gitea/framework/openai-dots/
   https://www.agent200.com/connectors/gitea/framework/claude-duet/
   https://www.agent200.com/connectors/gitea/framework/hermes-agent/
   https://www.agent200.com/connectors/gitea/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

## About

With the Gitea connector, your agent works in each user's own Gitea account. It can list repositories, read a file, find and open issues, comment on them, and list or open pull requests, using only the tools your project allows.

Gitea is a self-hosted Git service for code hosting, issues and pull requests.

## Gitea tools

- **List repositories** (`gitea_list_repos`, read): List the repositories the user can reach.
- **Read a file** (`gitea_get_file_contents`, read): Get the contents of a file in a repository.
- **List issues** (`gitea_list_issues`, read): List open or closed issues in a repository.
- **Create an issue** (`gitea_create_issue`, write): Open a new issue with a title and description.
- **Comment on an issue** (`gitea_create_issue_comment`, write): Add a comment to an issue or pull request.
- **List pull requests** (`gitea_list_pull_requests`, read): List pull requests in a repository.
- **Open a pull request** (`gitea_create_pull_request`, write): Open a pull request from one branch to another.

## Limits you can set

**Turn single tools on or off.** Let the agent read repositories and issues, and switch off `gitea_create_pull_request` so it can never open one.

**Restrict what the agent reaches.** Choose the endpoints and scopes a project may use, for example issues but not repository files. A call outside them is refused.

## Get started

### Step 1: Set up the SDK

Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Let your user connect Gitea

Each end user authorizes their own Gitea account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

File `connect.js`:

```js
// Each end user authorizes their own Gitea account, once.
const connection = await agent200
  .user("user_123")
  .connect("gitea");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 3: Run with the Gitea tools

Name the user, the model and the tools. The model decides which Gitea tools to call, and Agent200 executes them with that user's connection.

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "What issues are open in the billing repo",
    tools: ["gitea"],
  });

console.log(result.output);
```

(Conceptual example of the Agent200 SDK.)

## Sign-in and permissions

**Who signs in.** Each of your users, once, on their Gitea instance's own sign-in page. You never see or store their Gitea password.

**What access is requested.** The scopes the connection needs, such as reading repositories, writing issues or managing pull requests, listed on the Gitea authorization screen. Users can remove the app later from their Gitea account settings.

## Example requests

- "What issues are open in the billing repo"
- "Open an issue about the broken login redirect"
- "Show the README of the infra repository"
- "List pull requests waiting for review"

## Guides: Gitea with your AI framework

- [Gitea + Claude](https://www.agent200.com/connectors/gitea/framework/claude.md): Set up Gitea for Claude with Agent200, then check which tools are available to your agent.
- [Gitea + ChatGPT](https://www.agent200.com/connectors/gitea/framework/chatgpt.md): Set up Gitea for ChatGPT with Agent200, then check which tools are available to your agent.
- [Gitea + Claude Code](https://www.agent200.com/connectors/gitea/framework/claude-code.md): Set up Gitea for Claude Code with Agent200, then check which tools are available to your agent.
- [Gitea + Muse](https://www.agent200.com/connectors/gitea/framework/muse.md): Set up Gitea for Muse with Agent200, then check which tools are available to your agent.
- [Gitea + Grok Bot](https://www.agent200.com/connectors/gitea/framework/grok-bot.md): Set up Gitea for Grok Bot with Agent200, then check which tools are available to your agent.
- [Gitea + OpenAI Dots](https://www.agent200.com/connectors/gitea/framework/openai-dots.md): Set up Gitea for OpenAI Dots with Agent200, then check which tools are available to your agent.
- [Gitea + Claude Duet](https://www.agent200.com/connectors/gitea/framework/claude-duet.md): Set up Gitea for Claude Duet with Agent200, then check which tools are available to your agent.
- [Gitea + Hermes Agent](https://www.agent200.com/connectors/gitea/framework/hermes-agent.md): Set up Gitea for Hermes Agent with Agent200, then check which tools are available to your agent.
- [Gitea + OpenClaw](https://www.agent200.com/connectors/gitea/framework/openclaw.md): Set up Gitea for OpenClaw with Agent200, then check which tools are available to your agent.

## FAQ

### Who handles the Gitea OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Gitea.

### Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Gitea connection, never another user's. It cannot reach anything the user or Gitea has not authorized.

### Can I limit what my agent can do in Gitea?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

## Related connectors

- [GitHub](https://www.agent200.com/connectors/github.md): Read repositories and work with issues and pull requests as the connected user.
- [GitLab](https://www.agent200.com/connectors/gitlab.md): Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.
- [Bitbucket](https://www.agent200.com/connectors/bitbucket.md): List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.
- [Jira](https://www.agent200.com/connectors/jira.md): Search, create and transition Jira issues for the connected user.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
