Skip to content
Solutioneer

Connect GitHub

Solutioneer uses the Composio github toolkit for GitHub writeback. Three skills — demo-scenario-builder, integration-fit-gap-analyzer, and poc-handoff-orchestrator — write to GitHub.

Prerequisites

Section titled “Prerequisites”
  • A Composio API key in .env.
  • A GitHub account with permission to create issues in the target repo.

What gets connected

Section titled “What gets connected”

The github toolkit exposes this tool slug to Solutioneer:

  • GITHUB_CREATE_AN_ISSUE — create an issue in a target repository.

Solutioneer uses a deliberately narrow subset of the GitHub API. It does not create PRs, branches, releases, or commits.

How to connect

Section titled “How to connect”

The normal flow runs inside Codex:

  1. Ask for a GitHub write. For example: “Open a GitHub issue in sushii2/solutioneer for each POC risk.”
  2. Codex verifies that COMPOSIO_API_KEY is present.
  3. Codex checks whether the github toolkit is connected.
  4. If it is not, Codex offers Connect now / Skip.
  5. Connect now opens the Composio hosted login page in a browser tab.
  6. You complete the GitHub OAuth flow — typically including repository access scope.
  7. Codex polls the connected account until it becomes ACTIVE.
  8. Once active, Codex executes the write.

Connect from the Composio dashboard

Section titled “Connect from the Composio dashboard”
  1. Open the Composio dashboard.
  2. Go to Connections.
  3. Find the github toolkit.
  4. Click Connect and authorize the GitHub account.
  5. If you are authorizing an organization, grant the org scope you need.
  6. Confirm the connection shows as Active.

Which skills write to GitHub

Section titled “Which skills write to GitHub”
  • Demo Scenario Builder — can open a GitHub issue to track demo prep tasks.
  • Integration Fit Gap Analyzer — can open GitHub issues for gap and unknown rows when Linear is not your tracker of choice.
  • POC Handoff Orchestrator — can open GitHub issues per POC risk.

Confirmation rules

Section titled “Confirmation rules”

Codex confirms before writing. The target owner/repo, the issue title, and any labels are part of the destination confirmation. If you did not ask for a GitHub write, it will not push to GitHub.

Troubleshooting

Section titled “Troubleshooting”
  • Repo not found. The Composio connection must have access to the repo you named. For org repos, make sure the OAuth app has the org scope.
  • Permission denied. Issue creation requires write access to the repo. Private repos need an extra scope grant during OAuth.
  • Duplicate issues. Codex does not currently dedupe against existing GitHub issues. Run the skill once and review before re-running.

See Troubleshooting for more.