Contents
Getting started
Using Codepanion
Connecting your tools
Connect your team's tools and the agent can pull them into an investigation: searching existing issues, filing new ones, and reading your wiki. Connections live under Integrations in the app: one card per provider, each asking for the credential that provider issues.
Fill in what the provider needs, hit Test Connection to check it against the provider before you commit to it, then Save. The badge on each card tells you whether that provider is currently connected, and a provider only appears to the agent as a tool once it is. A connected card also says where it points, such as the site and project, and keeps those fields filled in, so replacing a token means pasting only the token.
Issue trackers
Connect an issue tracker and the agent can search existing issues and file new ones as part of an investigation. Codepanion ships four providers, and each needs the place its calls go as well as a credential. A save or test with any of it missing is refused and names the field, and the test checks that the credential reaches that place.
- JiraYour site URL, the Atlassian account email the token belongs to, the project key new issues are filed under, and an API token.
- GitHubThe repository, as
owner/name, and a personal access token that can read it. Use a fine-grained token limited to that one repository, with read and write access to Issues, Pull requests and Contents. A classic token works too, but it can reach every repository its owner can. - LinearThe ID of the team new issues are filed into (the team's UUID, not its short key) and a personal API key.
- SalesforceYour instance URL, such as
https://your-org.my.salesforce.com, and an OAuth access token. An access token expires with the Salesforce session that issued it (two hours by default), so paste a new one when searches start failing. Salesforce is read-only: the agent can search it, but Codepanion never writes there.
Once connected, the agent gains these tools:
search_issuesFind related issues so an investigation can build on what's already known.create_issueFile a new issue, matching your tracker's house style, when an investigation surfaces something worth tracking. Offered only for providers that can create issues, so it never appears for Salesforce.propose_changeTurn a proposed fix into a unified-diff patch. On GitHub it is attached to the issue as a comment, and a one-line change to an existing file also opens a draft pull request (see proposed code changes for when it won't); on the other trackers the patch is handed back in the thread.
Both of those write to your tracker, so neither ever runs on its own: the agent shows you exactly what it wants to send and waits for you to approve it. See approvals & write actions.
Searching first is much of the point of connecting a tracker. An investigation that finds the problem already on file links to it instead of duplicating it, and one that finds nothing drafts the new issue out of what the investigation established rather than out of the sentence you typed.
Docs sources
You can also connect a docs source: link Confluence (your site URL, Atlassian account email, and an API token) and the agent can search your team's wiki (runbooks, architecture notes, postmortems) and read the pages it finds:
search_docsSearch your documentation for relevant pages; each hit comes back with its title, link, and an excerpt.read_doc_pageRead a page's full content when an excerpt looks relevant, and cite it in the findings.
Note
Integration credentials are stored per tenant and used only for that tenant's investigations. More providers are on the roadmap; tell us which tracker you use.