Data & Privacy

Agent Note is designed for teams that want AI review history without a hosted backend. The permanent record is git-native, and the temporary working data stays inside the repository clone.

Short Version

No hosted service

Agent Note does not require an Agent Note server. PR Report and Dashboard run in your repository’s GitHub Actions.

Git-native history

Permanent records are stored as git notes under refs/notes/agentnote.

Local temp data

In-progress session files live under .git/agentnote/ and are not committed.

No telemetry

The CLI does not send prompts, responses, or file paths to an Agent Note service.

What Gets Stored

Agent Note stores the information needed to explain a commit:

Field	Purpose
prompt / response	Conversation that led to the commit
contexts[]	Display-only hints for short prompts
files	Committed files and whether AI touched them
attribution	AI Ratio, method, and line counts when available
agent / model	Agent and model metadata when exposed

Paths matched by the repository-root .agentnoteignore still stay in files; they are only excluded from the AI Ratio denominator.

The schema is shown in How It Works.

Before You Enable Dashboard

Question	Recommendation
Can everyone who sees Pages also read the prompts?	Enable Dashboard only when Pages visibility matches your repository policy.
Do prompts contain secrets or customer data?	Treat git notes like review data and avoid putting secrets in prompts.
Do you only need PR review context?	Use PR Report only and skip --dashboard.

Where It Lives

Layer	Location	Shared?
Session temp	.git/agentnote/sessions/	No
Permanent notes	refs/notes/agentnote	Yes, on git push
PR Report	Pull Request description or comment	Yes, in GitHub
Dashboard bundle	GitHub Pages artifact and gh-pages/dashboard/notes/*.json	Yes, if Dashboard is enabled

Note

Git notes are not regular files in your branch. They are pushed and fetched through the separate refs/notes/agentnote ref.

What Is Not Stored

Agent Note does not store everything the agent can see.

• It does not store your full workspace.
• It does not store shell command output as file evidence.
• It does not upload data to an Agent Note backend.

Note

With agents that expose trusted transcripts, Agent Note may still produce commit-level attribution from fresh transcript evidence recorded at commit time, without storing shell command output.

Team Visibility

Anyone who can fetch refs/notes/agentnote can read the stored prompts and responses. Treat git notes like review metadata: useful for collaboration, but still repository data.

If your repository includes sensitive prompts, keep repository and Pages visibility aligned with your team’s review policy.

Dashboard Privacy

Dashboard is optional. When enabled, it publishes a static view through GitHub Pages using the note snapshots produced by your workflow.

If you do not want a shared web view, use PR Report only and skip --dashboard.