Use GitHub from Claude
Add the GitHub connection to a Space that runs Claude, then use it from every channel in that Space.
Connect GitHub once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the GitHub connection to a Space that runs Claude, then use it from every channel in that Space.
Add the GitHub connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
GitHub hosts Git repositories along with the issues, pull requests, and Actions workflows that move code from idea to release. Shared into a type.com Space, the GitHub connection lets Claude or Codex file and triage issues, open pull requests, commit edits, comment with findings, and kick off workflow runs, while your engineers follow the same thread.
Connect GitHub once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Paste a customer report into the thread and the agent files a GitHub issue with a clear title, repro steps, and the right labels and assignee.
Create a GitHub issue in web-app for this checkout bug, label it 'bug' and 'p1', and assign it to Priya.
Have Codex commit a config or copy change to a branch and open a draft pull request with a written description and suggested reviewers.
Update the timeout in config/api.yaml to 30s on a new branch and open a draft GitHub PR describing why.
Dispatch a GitHub Actions workflow with the branch and inputs you name, then have the agent comment the outcome on the related pull request.
Dispatch the 'staging-deploy' GitHub workflow on release/2.4 and comment on PR 812 once it's started.
Files a new issue with title, body, labels, assignees, and milestone so work is tracked from the start.
Opens a pull request between two branches with a description, reviewers, and optional draft status.
Posts a comment on an issue or PR, useful for sharing review notes, test results, or next steps.
Commits new or changed file content to a branch, with an optional SHA check to avoid overwriting newer edits.
Starts a GitHub Actions workflow on a chosen branch with inputs, for releases, deploys, or test runs.
Adds labels and routing details to issues or pull requests to sort incoming engineering and support work.
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
GitHub's REST API uses https://api.github.com with token-based Authorization headers, API version headers, repository, issue, pull request, user, and organization resources.
Yes. With a GitHub connection shared to a Space, Claude or Codex can commit file changes, open pull requests, and comment on them. The work happens in a thread, so reviewers can see what the agent changed and why.
You can sign in with OAuth or supply a GitHub access token when an admin creates the connection. The admin then decides which Spaces can use it, and tokens never get pasted into threads.
The GitHub integration lists triggers such as a new branch, a branch change, and a new workflow artifact. You can also run recurring GitHub checks, such as a daily triage of unlabeled issues, as a type.com automation.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect AppDrag to Claude in type.com to execute cloud backend functions across dev, preprod, and production environments from a thread.
Connect LaunchDarkly to Claude in type.com to apply approved flag changes, copy flags across environments, and manage teams.
Connect Contentful to Claude in type.com to publish content types, archive assets, and manage releases from a shared editorial thread.
Connect Ably to Claude in type.com to check channel presence, history, and push subscriptions from a shared thread.