Integration: ticketing and approvals

GitHub work tracking AI cost on every issue

Argent Strategic Intelligence books each AI agent's spend to the GitHub issue it worked on, rolls it up, holds work at its cap, and writes the cost and a signed summary back to GitHub.

01 / INTEGRATION: TICKETING AND APPROVALS

AI spend on the GitHub issue it served

AI agents now write code, tests and documents against real work items, and their bill usually arrives as one number at month end. Argent connects to GitHub and books every agent's AI spend to the issue it worked on.

  • Your GitHub repositories, milestones and issues appear in Argent's Work catalog, kept in step with GitHub.
  • Each request that goes through Argent is priced on Argent's signed ledger and booked to the issue the agent declared, then rolled up through the milestone to the repository.
  • A budget can sit on the issue, the milestone or the repository. At the cap, the work waits for its budget owner.
  • The cost can be written back into GitHub, so the issue itself shows what its AI work cost.
02 / INTEGRATION: TICKETING AND APPROVALS

What Argent does with GitHub

StepWhat happens
Sync the boardArgent reads the repositories, milestones and issues on the boards you choose into its Work items, picking up where the last read stopped. GitHub wins on state: the sync reads and never overwrites.
Book the spendIn ADE, the Argent Development Environment, the developer picks the issue when launching a session, and the agent can declare the issue it is on with a tool. Each sub-agent's spend is kept separate. Argent books the session's priced spend to that issue, once.
Cap itAn admin sets a cap on an issue, milestone or repository, with a warning at 80 percent. At 100 percent, set to Pause, the next prompt of every ADE session on that work is held until the budget owner chooses Raise cap or One-time overage.
Write the cost backA cost value on each synced issue, equal to its lifetime AI spend and rewritten only when it changes.
Write the work backOn commit, ADE drafts one summary comment (what changed, which files, the cost of that stretch). The developer approves it, Argent removes secrets, signs it and posts it to the issue. Closing the issue in ADE can close it in GitHub too.
03 / INTEGRATION: TICKETING AND APPROVALS

How the cost shows up in GitHub

Each synced issue can show its lifetime AI spend inside GitHub.

Argent writes an issue's cost into a Number field on the issue's item in the repository's board Project. An issue that is not in that Project, or a connection with no Project fields named, gets the cost as one comment on the issue instead, kept up to date in place.

  • Values are absolute, never increments, so a missed run cannot double-count.
  • A field or permission GitHub refuses shows as a cost error on the connection, with a fixed plain sentence and a signed row, never silently.
  • Cost write-back has its own switch per connection.
04 / INTEGRATION: TICKETING AND APPROVALS

How it connects

Argent talks to GitHub's API over HTTPS, as the GitHub App's bot.

  • Credential: a GitHub App, installed once per organization; Argent stores the installation id per organization and posts as the app's bot.
  • No secret in Argent's database. The credential stays in your vault and Argent stores a reference to it. Works with HashiCorp Vault and OpenBao, AWS Secrets Manager, CyberArk Conjur or Infisical.
  • Guarded calls. Every call goes through Argent's protected HTTPS client, which refuses private addresses and redirects to other hosts. Calls go to GitHub's API at api.github.com.
  • Bounded sync. Each run reads a capped amount, so a misbehaving server cannot stall Argent or fill its database.
  • Plain errors. Failures are stored as fixed codes and sentences; GitHub's own response text is never kept.
05 / INTEGRATION: TICKETING AND APPROVALS

What you configure

  1. Create the GitHub credential: a GitHub App, installed once per organization; Argent stores the installation id per organization and posts as the app's bot. Store it in your vault.
  2. Connect GitHub in the Argent console under Work, Trackers, with the address and the vault reference.
  3. Pick the boards to sync. Argent maps GitHub's repository, milestone and issue to its own project, feature and story levels.
  4. Turn on the write-backs you want. Every switch ships Off: Summary comment, and Close the issue as completed, and, with a GitHub Project chosen, Project status on close (default Done).
  5. Name the cost fields and switch cost write-back on for the connection.
  6. Set budgets on the work items that need a cap, and say whether 100 percent pauses or only alerts.

Spend is booked for agents that work through Argent; ADE is where the developer picks the issue and the agent declares it.

06 / INTEGRATION: TICKETING AND APPROVALS

Signed, and GitHub stays in charge

Every write-back is signed in Argent's ledger before it is posted, and refused if the ledger is down.

  • The Tracker sync trail lists each write: the person, the GitHub issue, COMMENT, STATUS CHANGE or CLOSE, and POSTED, RETRYING or REFUSED BY TRACKER.
  • Each comment ends with Posted by Argent on behalf of <person>, agent <agent>. and its record id.
  • If someone already moved the issue in GitHub, the tracker wins: Argent leaves it as GitHub has it.
  • No agent can lift a hold or approve its own comment: every write an agent asks for waits for its human owner.

Hand the trail to an auditor with one-click audit evidence.

07 / INTEGRATION: TICKETING AND APPROVALS

Where this fits

Browse all integrations.