Skip to main content

GitHub Integration

Manasvi can read from GitHub — repositories and issues — through governed tools. Like every tool, a GitHub call goes through policy evaluation and the execution chain; the API gateway holds the token and makes the actual request.

This first version is read-only. Write actions (creating issues, comments, etc.) are intentionally not included yet — they belong behind an approval gate, following the same pattern as Gmail and Calendar writes.

Tools​

ToolWhat it does
tool.github-list-reposList repositories the connected account can access
tool.github-list-issuesList issues for a repository (pull requests are flagged)

Both are read-only, and their results are treated as untrusted external content — they can't silently become trusted memory or authority.

Configure​

Create a GitHub personal access token with read scopes (e.g. repo for private repositories, or public_repo for public only) and set it on the API gateway:

GITHUB_TOKEN=ghp_xxx

Restart the gateway. When the token is unset, the GitHub tools return a clear GITHUB_NOT_CONFIGURED error instead of failing silently.

Use​

Ask the agent naturally, for example:

  • "List my GitHub repositories."
  • "Show the open issues in acme/manasvi."

The agent proposes the matching tool; policy allows the read; the gateway calls GitHub and returns normalized results.

Notes​

  • The token lives only on the gateway, never in the sandbox or in prompts.
  • Read tools are allowed without approval by default policy; if you later add write tools, gate them behind approval like the Gmail/Calendar write actions.