Small Medium Teams

Your repositories, read from chat.

Ask the assistant to list your repositories, read and search code, review pull requests, and triage or open issues. GitHub stays the source of truth — you just stop tab-hopping to find what you need. Every call is scope-gated and logged to the central audit ledger; PII redaction of code is opt-in (off by default so it never mangles your source).

Stop context-switching to GitHub

Ask the question. Read the code. Open the issue.

You

“Which of my repos changed in the last week?”

Other Me

Three repositories had pushes in the last 7 days: api-gateway (12 commits), web-client (5 commits) and infra (2 commits). Want the recent commit messages for any of them?

You

“Search api-gateway for where we set the JWT expiry and show me the code.”

Other Me

Found it in auth/tokens.py line 48 — JWT_TTL = timedelta(minutes=15). There’s a matching refresh-token TTL of 7 days two lines below. Want me to pull the full function?

You

“Open an issue in web-client: ‘Login button unresponsive on Safari 17’ — label it bug.”

Other Me

✅ Opened web-client #312 “Login button unresponsive on Safari 17”, labelled bug.

You

“Any open pull requests on api-gateway waiting on review?”

Other Me

Two open PRs: #88 “Add rate limiting” (3 files, awaiting review) and #91 “Bump deps” (CI green). Let me know if you want a summary of the diff on either.

What the assistant can do

Read repos, code, issues and pull requests — plus open and comment on issues, every call SCRS-gated.

github_list_repos
List the repositories the connected account can see — name, visibility, default branch, last push.
github_read_file
Read the contents of a file at a path (and optional ref) in a repository for inline display in chat.
github_search_code
Search code across a repository (or the account) and return file paths, line numbers and matching snippets.
github_search_issues
Find issues by repo / state / label / assignee / text. Returns number, title, state, labels and assignee.
github_get_issue
Full detail for one issue — body, labels, assignees and recent comments, flattened for readable chat display.
github_create_issue
Open a new issue in a repository. Accepts title, body, labels and assignees.
github_comment_issue
Post a comment to an existing issue or pull request.
github_list_pull_requests
List pull requests by repo / state. Returns number, title, state, head and base branches.
github_get_pull_request
Full detail for one pull request — description, changed files, review state and recent comments.

Every call is governed

SCRS dual-gate, tier check, audit ledger — on every GitHub tool call.

Gate A — Tier Gate

Re-checks the user’s plan at tool-call time, not just at OAuth connect. A downgrade revokes GitHub tool access immediately.

Gate 1 — Scope Gate

Users or admins can disable the Repositories data collection. When disabled, every GitHub tool blocks at call time with a clear message.

Gate 2 — DLP Scan

On create-issue / comment, the LLM-synthesised arguments are scanned for PII and secrets before they leave your server. Block-only — the gate refuses to silently corrupt an issue body.

Audit Ledger

Every call writes a hash-chained row to SCRSAuditLog with gate=tool. Forwards to your SIEM via the same drain the rest of SCRS uses.

Two minutes to connect

  1. 1

    Settings → Integrations → Connect GitHub.

  2. 2

    Authorise the Other Me GitHub App and choose which repositories it can access — all of them, or a hand-picked subset.

  3. 3

    Access is scoped to exactly the repos you select — nothing outside that list is visible to the assistant.

  4. 4

    Start asking. Every call is scope-gated, DLP-scanned on writes, and audit-logged.

Read your code without switching tabs.

Connect GitHub, keep your governance. 3-day business trial — card at signup, no charge for 3 days.

Start my trial