Gitea

Developer tools

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.

About Gitea

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.

Tools

What your agent can do in Gitea.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Gitea connection.

  • List repositories

    Read
    gitea_list_repos

    List the repositories the user can reach.

  • Read a file

    Read
    gitea_get_file_contents

    Get the contents of a file in a repository.

  • List issues

    Read
    gitea_list_issues

    List open or closed issues in a repository.

  • Create an issue

    Write
    gitea_create_issue

    Open a new issue with a title and description.

  • Comment on an issue

    Write
    gitea_create_issue_comment

    Add a comment to an issue or pull request.

  • List pull requests

    Read
    gitea_list_pull_requests

    List pull requests in a repository.

  • Open a pull request

    Write
    gitea_create_pull_request

    Open a pull request from one branch to another.

Control

Limits you can set.

You decide what your agent may do in Gitea, and Agent200 runs every call within those limits.

  • 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

Connect Gitea
in three steps.

  1. 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.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 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.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // 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);
    }
  3. 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.

    run.js
    Conceptual example
    Run a request with the connector's tools
    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);

Access

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.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Gitea connector and how to use it.

Agent brief
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/

This page is also available as Markdown, for agents and LLMs: /connectors/gitea.md

Guides

Use Gitea with the AI you build on.

Step-by-step setup for Gitea with a specific model, assistant or agent framework.

FAQ

Gitea and Agent200, answered.

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.

  • GitHub

    GitHub

    Read repositories and work with issues and pull requests as the connected user.

    Managed OAuth Developer tools
  • GitLab

    GitLab

    Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.

    Managed OAuth Developer tools
  • Bitbucket

    Bitbucket

    List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.

    Managed OAuth Developer tools
  • Jira

    Jira

    Search, create and transition Jira issues for the connected user.

    Managed OAuth Developer tools
200 OK

Start with Gitea.
Your agent does the rest.

Your users connect their own Gitea accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)