Repository navigation
feat(web): analytics disclosure and owner dashboard discoverability - #187
Conversation
…hboard - /agents/register gets an #analytics section in plain language: what is counted, the daily per-handle visitor pseudonym (not an identity), what is never stored, how to open the 15-minute single-use dashboard link, the 7/30 day views, and immediate revocation on token rotation or deletion. - Checklist step 4: the one sentence to ask your agent for the dashboard. - /u/<handle> and the directory point owners to the dashboard. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Session-Id: 8fa30995-3394-4357-aadf-23aee1464578
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to The disclosure links and dashboard guidance have no identified issue that needs resolution before merge. Pre-merge checks |
  |
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Docstring Coverage |  |
Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 5 files. (1 skipped: 1 … | Write docstrings for the functions missing them to satisfy the coverage threshold. |
✅ Passed checks (4 passed)
-
Check name Status Explanation Title check The title clearly and concisely describes the main changes: adding analytics disclosure and improving owner dashboard discoverability across the web pages. Description check The description is directly related to the changeset and provides relevant details about the analytics disclosure, dashboard pointers, affected pages, and tests. Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
-
Explanation
Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 5 files. (1 skipped: 1 unsupported.)
- Fix all pre-merge checks with AI
✨ Finishing Touches 💡 1
-
📝 Generate docstrings 💡
-
-
- Commit to this branch
- Create a new PR
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
A rabbit reads the metrics page,
Then finds the dashboard link in place.
It hops through notes on what is stored,
And checks the link’s brief ticking chord.
With one last hop, it cheers the change!
Comment @coderabbitai help to get the list of available commands.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
…-company state Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Session-Id: 8fa30995-3394-4357-aadf-23aee1464578
|
@codex review |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
All reported issues were addressed across 6 files
Reply with feedback, questions, or to request a fix.
View guided diff | Turn on auto-fix | Re-trigger cubic
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
There was a problem hiding this comment.
All reported issues were addressed
Reply with feedback, questions, or to request a fix.
View guided diff | Turn on auto-fix | Re-trigger cubic
|
Preview deployed!
This is a Cloudflare Workers preview version of this PR's build. |
- Register page: the dashboard link is a single-use bearer token, so the intro now says numbers are visible to link holders and to keep it private, instead of promising owner-only visibility. - Directory: link the 'what arelay.to measures' disclosure with descriptive text instead of 'analytics dashboard'. - Keep the URL constants together; DASHBOARD_PROMPT moves below them. - Tests: plain phrase literal; render the directory in both states and assert the real href instead of grepping component source.
2 participants
This is the human-language half of
docs/ANALYTICS_BRIEF.md§7, item 4 (customer docs). The agent-guide half is AgentWorkforce/relay-agent#36, which adds "## 4. Analytics and your owner dashboard" toarelay.to/register./agents/register
#analyticssection, "Analytics and your dashboard":POST /api/v1/agents/<handle>/manage/dashboard-linkand returns a single-use, 15-minute link that never contains the token. You open it and choose Open dashboard. The dashboard shows 7- and 30-day views.Discoverability for owners
#analytics. This applies to both the page andchecklist.md./u/<handle>(active profiles): "Own this agent? Ask your agent for your private analytics dashboard link", with a link to the disclosure./directory: the register note adds "Owners get a private analytics dashboard". This is a one-line change; arelay-dir is informed.Every statement matches the shipped relay-agent code and the live dashboard flow, including the confirm-before-redeem step.
Tests
tscis clean,npm run buildsucceeds, andverify:recommended-flowspasses.🤖 Generated with Claude Code
Note
Low Risk
Documentation and marketing copy only; no changes to analytics collection, dashboard APIs, or auth flows.
Overview
Adds human-facing analytics disclosure and makes the owner dashboard easier to find across registration, directory, and agent profile pages—copy and links only, no analytics or API behavior changes.
On
/agents/register, a new#analyticssection spells out what arelay.to counts, how daily visitor pseudonyms work, what is never stored, how to get a one-time 15-minute dashboard link viaPOST /api/v1/agents/<handle>/manage/dashboard-link, and how token rotation revokes access. The “What you get” dashboard bullet now links there instead of inlining the long explanation.agent-register.tscentralizesREGISTER_ANALYTICS_ID,REGISTER_ANALYTICS_URL, andDASHBOARD_PROMPT. The registration checklist (page and Markdown) gains §4 Your analytics dashboard; Support moves to §5.Discoverability:
/directoryand/u/<handle>add short owner CTAs linking to the disclosure; directory empty state gets matching note styling. Tests assert the disclosure copy, checklist section, directory links, and profile pointer.Reviewed by Cursor Bugbot for commit 4246a1e. Bugbot is set up for automated code reviews on this repo. Configure here.
Agent Relay sessions
claudesession8fa30995· opened viagh pr create· last active 2026-10-09