Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.anyshift.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

When Annie identifies a concrete code change in an investigation, that change can be promoted to a pull request with one click. Annie reads the relevant repository, drafts the diff, and opens the PR against the default branch with a summary of the reasoning and a link back to the conversation in Anyshift. Propose Fix is available on:
  • RCA hypothesis cards — when a hypothesis points to a specific code remediation, the card carries a Propose Fix button.
  • Chat answers — when a chat reply describes a specific code change, one or more Propose Fix cards appear below the answer (one per proposed change).
The same coding agent and the same review experience apply to both surfaces.

​
Requirements

Propose Fix requires two GitHub App installations on your organization. They are separate apps with distinct permission scopes, so the investigation and write-capable surfaces remain isolated.

Investigation App

anyshift-app — read-only access used for navigating code, reading PRs and issues, and following commit history during investigations. Installed via Integrations → GitHub → Connect GitHub Organization. Required for every Anyshift workspace.

Agentic App

anyshift-agentic-app — write-capable access used exclusively by Propose Fix to create branches, push files, and open pull requests. Installed via Integrations → GitHub → Enable write mode. Required for Propose Fix. Without it, the Propose Fix CTA does not appear and Annie will not attempt write actions.
In addition, the repository touched by the proposal must be linked to the Anyshift project that produced the RCA or chat answer. Unlinked repositories never surface a Propose Fix CTA, even when an investigation references their code.

​
What clicking it does

1

Click Propose Fix

The card switches to a “Working on it…” state. You can leave the page; the run continues server-side and the card reflects status when you return.
2

Annie writes the change

A dedicated coding agent reads the repository, locates the file and function the hypothesis or answer pointed to, and produces a minimal, focused diff. The agent runs in isolation from your investigation conversation, so the RCA or chat is unchanged.
3

A pull request is opened on GitHub

The PR is opened by the Anyshift Agentic App against the repository’s default branch. The PR body contains the originating context (RCA hypothesis or chat excerpt) and a link to the conversation in Anyshift.
4

The card shows the PR link

The card is replaced inline with a link to the pull request. Clicking opens the PR in a new tab. A single proposal may produce more than one PR if the fix spans repositories; each PR gets its own link.
End-to-end latency runs from a few seconds to a couple of minutes depending on the size of the repository and the change.

​
States the card can show

  • Idle — a “Fix - Open PR” button. Click to trigger the run.
  • Running — a “Working on it…” badge with a spinner while Annie produces the diff and opens the PR.
  • Success, PRs opened — one or more pull request links. Clicking opens them in a new tab.
  • Success, no change needed — the coding agent concluded that the repository did not actually require a change. No PR is opened.
  • Failed — an error message and a Retry button. Retry starts a fresh run from the same proposal.
Clicking the trigger again while a run is already in flight is a no-op — the in-flight run is reused.

​
Review and merge

The pull request goes through your normal review process: branch protections, required reviewers, CI checks, and merge policies all apply unchanged. Annie’s PR is a regular PR.
The fix is a proposal, not a deployment. Nothing reaches production until a human merges. Treat the PR like any other diff: read the change, run CI, request adjustments in review.
If the PR needs adjustments, comment on it like you would for any teammate. Annie does not currently iterate on review comments automatically. If the proposed fix is wrong, close the PR and capture the correction as feedback to refine the next investigation.

​
Re-running

  • From a failed state, the card exposes a Retry button that triggers a fresh run from the same proposal.
  • From a success state, there is no in-product re-run today. The PR link persists as the proposal’s outcome.
A successfully opened PR remains linked to its originating hypothesis or chat answer indefinitely, preserving the postmortem trail (investigation → proposal → PR → commit).

​
What appears in the PR

A concise title describing the change, followed by a short summary of why the change is being proposed. The summary is generated from the originating hypothesis or chat content, not boilerplate.
A minimal change, scoped to the file or files the proposal pointed to. Annie does not bundle unrelated refactors into the same PR.
Commits and PRs are authored by the Anyshift Agentic App. The PR’s author appears as the App. Reviewers and assignees are not set automatically; configure them via your repository’s CODEOWNERS or PR templates if you want a default reviewer.

​
Disabling Propose Fix

Propose Fix is gated on the presence of the Anyshift Agentic App installation. To suppress the CTA and prevent any pull request from being opened:
  • Across the entire organization: uninstall anyshift-agentic-app from your GitHub organization. The investigation app (anyshift-app) stays installed and all read-only features (RCA, knowledge, navigation) continue working unchanged.
  • For a specific repository: in the Agentic App’s installation settings on GitHub, remove the repository from the selected list. Propose Fix CTAs for that repository disappear; other repositories keep the feature.
There is no per-project toggle inside the Anyshift product; the gate is the agentic-app installation itself.

Root Cause Analysis

How Annie produces the hypotheses Propose Fix acts on.

GitHub integration

Install and permission the Anyshift GitHub Apps.