1Pending
Enable your organization
An organization owner enables the shared workspace.
GitHub verifies your owner role before the workspace is enabled.
Local onlyPersonal analytics from supported local folders. Stored on this computer; GitHub is not used.
Synthetic demoExample sessions and prompts. No personal telemetry has been collected.
Workspace / Overview
Ready to connect
f↗FootPrint BY BORNWEST
A CLEARER VIEW OF YOUR TEAM'S AI WORKUnderstand your
Understand your
agent work.
Connect your GitHub organization and see how coding agents support your team, repository by repository.
◉ Continue with GitHub ↗Start with your GitHub account. Choose your personal workspace or a GitHub organization, then connect your device.
LOCAL WORK → SHARED UNDERSTANDING
◫
Your repositoriesCodex · Claude Code · and more
↓
FOOTPRINT WORKSPACE
One team. A clearer picture.
Sessions Models Reported usage
You choose what prompt content to share.
Collection starts after you set up the local utility.
GitHub verifiedVerified GitHub identity and repository access establish visibility.
Locally collectedOnly activity from enrolled GitHub checkouts.
Privacy by choicePreview your data and choose a prompt mode.
f↗FootPrint PERSONAL · LOCAL ONLY
YOUR WORK, ON YOUR COMPUTEROpen your local workspace.
Use the private launch link printed by your running FootPrint local server. It establishes access in this browser without GitHub.
The link contains a local access secret. Keep it private; FootPrint removes it from the address bar before connecting.
PERSONAL · LOCAL ONLY
No GitHub account neededSettings
Connect your local collector and choose what to save.
Keep personal collection separate
The local server stores data persistently in its own directory. These commands use a separate collector state directory and do not change your organization enrollment.
Run these from an installed FootPrint utility, or replace footprint with python3 -m agent_reports in the source checkout. The key-file path must match your local server's data directory.
Doctor checks source locations and supported formats without printing prompt bodies. Preview shows eligible data locally. Start begins collection after enrollment. Backfill of older history requires an explicit choice.
FootPrint reads supported local logs; it does not record the screen or capture every prompt entered into every app. Amp requires explicit capture. Source gaps and unknown usage remain visible.
WORKSPACE
GitHub verifiedSettings
Connect devices and manage workspace access.
Connect your GitHub repositories
Install GitHub App ↗Choose where the FootPrint GitHub App is installed. Your current GitHub access still limits what you can view. Refresh after changing an installation.
◫
Connect a GitHub workspace
Install the FootPrint GitHub App for your personal repositories or organization, then refresh. Accept any pending membership or organization approval in GitHub.
2
Install and connect FootPrint
Each teammate authenticates and connects their own device.
CLI release not configured
The server has not published a CLI release yet. An installation command appears here when a release is available.
Install from a provided source checkout
Until the public release is available, your workspace operator can provide the FootPrint source. From that checkout, with Python 3.9+ and Git installed, run:
python3 -m pip install .This installs the local utility. Continue with the organization and privacy setup below.
FootPrint reads supported local agent logs from enrolled GitHub checkouts. It excludes assistant output, reasoning, tools, and source-code files. Prompt bodies may contain code or private information. Permitted workspace viewers can inspect shared prompts.
Setup signs in with GitHub and previews eligible activity before you confirm collection. Historical backfill is a separate choice.
Already installed?
For a user-local release before 0.2.4, bootstrap once without repeating setup:
Then run footprint update. Public Homebrew installs use brew update && brew upgrade bornwest/tap/footprint. Keep your existing enrollment.
A device’s state directory belongs to one GitHub account and one organization. Use a separate --state-dir for another organization.
3
Watch your first activity arrive
Connectivity and collected activity are separate signals.
○
Device enrolled
Waiting for a collector heartbeat.
○
Collector online
Waiting for a recent collector heartbeat.
○
First activity received
Run an agent in an enrolled organization repository after starting the collector.
Your device status is available here. Repository analytics follows your verified GitHub access and the workspace access policy.
Workspace access
Choose a GitHub teammate and their FootPrint role. Repository visibility follows verified GitHub access.
Recent access audit
Choose a smaller analytics scope
This read exceeded the server’s memory budget. No partial totals were returned. Select a repository or a shorter UTC date window and retry.
Loading organization analytics…
WORKSPACE
Usage
Sessions, turns, and reported tokens.
Private workspaceWaiting for first event
More filters 0
Explore usage ↗
◫
Your usage will appear here
Connect a device to start collecting activity.
SELECTED RANGEAll collected records
Sessions
—Agent conversationsUser turns
—Recorded prompt turnsReported tokens Partial usage
—From supported local recordsDaily activity
Observed activity by UTC date.
Repositories 0
| Repository | Sessions | Reported tokens |
|---|
Recent sessions
Usage details
Missing usage remains unknown.
- Repositories
- —
- Input tokens
- —
- Output tokens
- —
Fixed UTC periods use your repository and advanced filters. Selected date filters apply to the overview above.
Today UTC
—Reported tokensThis month UTC
—Reported tokensAll history UTC
—Reported tokensMeasurement coverage
Sessions 0
Inspect prompt history and reported usage for each local session.
| Session / project | Member | Agent / model | Reported tokens | Turns | Usage / calls | Cache read | Reported cost | Last activity |
|---|
Usage records are observed source contributions, including cumulative deltas. They are not counted as model calls. Source estimates may cover only part of the usage.
About origins and privacy
User prompts includes human and unknown records, excluding detected agent and system messages. Unknown records are not proven human; choose Human only for strict source identification. The uploader is not proof of the original author.
Prompt content follows the collector’s privacy mode. An empty body can still represent a prompt record. Origin filters do not change token or usage totals.
Project breakdown 0
Folders within enrolled repositories or local workspaces.
| Repository / project | Sessions | User turns | Reported tokens | Cache read | Reported cost | Last activity |
|---|
Team members 0
Activity attributed to each authenticated uploader.
| Member | Sessions | User turns | Reported tokens | Cache read | Reported cost | Last activity |
|---|
Activity calendar
Reported tokens per UTC day. Select a day to inspect its sessions.
No records / measured zeroMoreUnavailable
A day with no records does not establish that the collector was running. Striped days have observed activity but unknown token totals. Chart gaps are unmeasured days. Trend changes are not a productivity comparison.
Model usage
Model share
Sources and adapter coverage
Adapter coverage
Agent turns
Reported model tokens
STORED ACTIVITY → REVIEWABLE PRACTICE
Prepare prompt suggestions, repository skills, team playbooks, and plans from the evidence you can access. Templates use stored telemetry. Nothing runs or installs in your repository.
Save a reviewable draft
A deterministic draft based on the selected repository and permitted stored records.
Saved drafts
Review status stays with each draft. Copy Markdown for manual adoption.