Settings

Connect the repository

Install the GitHub App and choose only the repositories you want to connect. Then return here and refresh.

Why the GitHub App needs write access

Reports are read-only. Setup needs write access to prepare a reviewable pull request. It never writes directly to your default branch.

• Metadata read access identifies the repositories you select.
• Code write access creates the setup branch and adds the attribution runtime.
• Workflows write access adds the publishing workflow to that branch.
• Pull requests write access opens the setup pull request.
• Actions variables write access sets the two public service URLs. These values are not secrets.

Review and merge the setup pull request to enable publishing. The trusted GitHub Actions workflow then uses its own token to update PR descriptions with attribution.

In GitHub, choose Only select repositories to limit the installation. You can change that selection in the installed app configuration.

Reports cover branches in the same repository. Fork pull requests are not supported.

Create the hosted publishing pull request

Choose a connected repository. Attribution opens a reviewable pull request on a dedicated branch that adds the trusted workflow and runtime, and sets the two public URL variables. Nothing is installed on a developer's computer.

Enable local capture in every developer clone

Local capture records coding sessions and publishes metadata during an ordinary Git push. Use the source revision that matches this service.

Loading the source revision for this service.

Read the authorized source installation guide. You need access to the private source repository and Python 3.11 or later.

Enter both paths to generate the required local install command.

Enter an unused source folder path and wait for the service revision to prepare the matching release.

Use an unused folder for a new source checkout. If you already installed this exact revision, skip preparation. Replace python3.11 with your Python 3.11-or-later executable if needed.

Your local installation command will appear here.

Run this once in each clone, restart Codex or Claude Code, and review the hook changes when your tool prompts you. Keep the Attribution checkout at this path. This command does not create or merge the hosted setup pull request.

Review, merge, and verify

Merge the setup pull request into the default branch. Then start a branch, make an edit with Codex or Claude Code, commit it, push normally, and open a pull request.

The hosted setup sets the URL variables for you. Use these commands only to inspect or repair them. The values are URLs, not secrets.

Select a repository to generate configuration commands.

Select a repository to generate verification commands.

Look for a successful Coding attribution footer run and a report link in the pull request description. If no report appears, run attribution doctor, inspect the failed workflow log, confirm both URL variables, and push a captured commit without --no-verify.