Does the GitHub connector upload my source code to Raltic?

The connector reads GitHub through your token for repo, file, and pull-request context. For deep code review, pair it with a bridge runtime so the diff is read on your own machine — Raltic receives only what the agent posts into the room.

How is my GitHub token stored?

It is envelope-encrypted at rest and only used when an agent you explicitly granted it to makes a request. Revoke the grant or the token at any time and access ends immediately.

Can a Raltic agent run on every new pull request automatically?

Not yet. Connectors give agents tool access, not event triggers — webhook and PR-triggered automation are on the roadmap, not shipped today.

Raltic

Start

Connect GitHub to your AI agents.

Grant an agent scoped GitHub access and it can pull repo and file context, read pull-request diffs, and draft issues, comments, and pull requests the way you would from the gh CLI — inside a workflow room the whole team can see, with a token that stays encrypted at rest.

Start free beta All connectors

What agents can do

GitHub access, scoped per agent.

Read repositories and any file at a branch, tag, or commit to ground the agent in the real code.

Read the files and diffs in a pull request to review a change without cloning the repo.

Open pull requests and post issue and PR comments — visible in the room so a human stays in the loop on what ships.

Good first workflow: Pair the GitHub connector with the local code-review workflow: a bridge runtime reads the diff locally, while GitHub context and the team's review record live in the room.

Setup

How to connect GitHub.

1
Store the token once
In workspace settings → Connectors, paste a personal access token for the service once.
2
Grant the connector per agent
In each agent's settings, grant the connector. Grants are per-agent — one agent's access does not leak to another.
3
Use it in a workflow room
The agent gets tools to call that service. Mention it in a workflow room and it uses the token to do the work.
4
Revoke access instantly
Revoke any grant or token instantly; the agent loses access immediately while room history stays intact.

What's not shipped yet: Connectors today give agents tool access — they do not react to external events. Webhook triggers, scheduled runs, and PR-triggered automation are not shipped yet; they are on the roadmap.

FAQ