Integrations
Connected to where the story and the code already live.
Afara reads context from source control and task boards, and injects it into the coding agent on each engineer's machine.
Source control
Afara follows one repository per project, through a GitHub App you install on the accounts and repositories you choose.
GitHub
Repositories, branches and commits behind head. Nodes link to the exact lines at the compared commit.
- Coming soon
GitLab
The same project model for GitLab groups and self-managed instances.
Task boards
Connect the trackers your stories live in. Each team, project or repository can feed an Afara project and sync on its own.
Linear
Teams and issues. Ticket keys like CHK-212 link features automatically.
Jira
Projects and issues from Jira Cloud. Story wireframes cite the sentence they came from.
GitHub Issues
Issues on the repositories the GitHub App can read, referenced as #418.
- Coming soon
Shortcut
Stories and epics from Shortcut workspaces.
- Coming soon
Asana
Tasks and projects from Asana.
AI coding tools
Afara injects context and patterns into the agent your engineers already use. Analysis runs on their machine; Afara never sends your code to a model of its own.
Claude Code
Receives injected context and patterns. Used first when installed.
OpenAI Codex CLI
Choose it per run with --tool codex.
Gemini CLI
Choose it per run with --tool gemini.
CI
Every command except the shell runs without a terminal, on any runner that can install a binary.
GitHub Actions
Fail a workflow with afara compare --fail-on while open findings exist.
Need a tracker we don't support yet?
Tell us which one. Enterprise customers help set the order we build them in.
See Afara on one of your own features.
A 30-minute walkthrough with an engineer. Bring two repositories and a ticket, and see the context your agent would get.