Code & Dev Tools · Token

GitHub

Issues, pull requests, code search and repository files, through GitHub’s own server.

Ask your agent

Once it is connected, ask for things like these.

  1. 01

    “List the open issues labelled bug”

  2. 02

    “Summarise what pull request #42 changes”

  3. 03

    “Find where we call the payments API in our repo”

How to connect

Connect it in the app, then give it to an agent.

  1. Step 01

    Get a personal access token.

    Needs the repo scope (add read:org if the agent should see organisation repositories). Encrypted on this computer, never in the workspace database.

    Create a token on GitHub
  2. Step 02

    Open Connectors in Lobstack and choose GitHub. Paste it in.

    Default ownerOptional
    The GitHub account or organisation the connector is labelled with, so people sharing a workspace can tell whose GitHub it is. It does not limit what an agent can reach; the token decides that.
    Allow changesOptional
    Off, an agent can read issues, pull requests and code but not open, comment on, push or merge anything. An agent with a repository can still push its own branch without this.
  3. Step 03

    Give it to an agent.

    An agent reaches only the connectors you give it.

Tools

What it gives an agent.

Examples. The server decides the real list when it starts.

  • search_issues
  • issue_read
  • list_pull_requests
  • get_file_contents
  • search_code
Agents that use it

Ready-made agents that work on GitHub.

All agents.

More connectors

More in Code & Dev Tools, and where most teams start.

All connectors, on their shelves.