Skip to content

feat(dashboard): 'Connect your agent' panel (API token UI) — landed post-#11#13

Merged
Coding-Dev-Tools merged 1 commit into
mainfrom
fix/connect-agent-panel-urls
Jul 15, 2026
Merged

feat(dashboard): 'Connect your agent' panel (API token UI) — landed post-#11#13
Coding-Dev-Tools merged 1 commit into
mainfrom
fix/connect-agent-panel-urls

Conversation

@Coding-Dev-Tools

Copy link
Copy Markdown
Owner

What

The agent-connect backend (per-user tokens, /api/remember, gate) merged in #11, but the frontend panel commit (b30b81c) was not in that merge — so main has the API with no UI to mint tokens. This PR adds the fixed panel.

What it adds (Settings → new 'Connect your agent' card, team-mode only)

  • Lists the signed-in member's per-user API tokens.
  • Create: label + one-time token shown once, with a ready-to-paste Authorization: Bearer … line.
  • Revoke.
  • Hidden with a hint when team mode is off.

Includes the two fixes I made during the accuracy review

  • Correct snippet URLs: POST <base>/api/remember / GET <base>/api/recall (the earlier version dropped /api).
  • renderTokList() split out so creating a token doesn't re-render the panel and wipe the one-time token before the user can copy it.

Verified

  • node --check on the inline JS: OK. LF line endings (no CRLF pollution).
  • test_dashboard_v2.py + test_agent_connect.py: 46 passed. Dashboard serves 200 with the card present.

Notes

  • This is the panel that was on feat/agent-connect (b30b81c + fix 2f9d474), applied to current main (whose index.html had no panel). The backend it calls (/api/auth/token, /api/auth/connect-info, /api/remember) is already on main from feat(agent-connect): per-user API tokens + Team-gated /api/remember #11.
  • Not merging (per your instruction) — opening for review.

Settings gains a 'Connect your agent' card (team mode only): lists the signed-in
member's per-user API tokens, creates one (label + one-time token shown once with a
ready-to-paste 'Authorization: Bearer ...' line), and revokes. Wired into loadSettings().
This UI was developed on feat/agent-connect but did not land in the #11 merge (only the
backend did), so main had the agent-connect API with no UI to mint tokens. This adds the
fixed version (renderTokList so the one-time token is not wiped on re-render; correct
/api/remember + /api/recall snippet URLs).
@Coding-Dev-Tools

Copy link
Copy Markdown
Owner Author

Council Gate Verdict — APPROVE_WITH_NITS

Risk level: high | Agreement: 0.5 | Council session: council-fd8f497f-b817-4f95-8973-77c8a13f23c4

Per-model scores (rubric: correctness / safety / style / tests / complexity)

  • openrouter/meta-llama/llama-3.1-70b-instruct:free: REWORK (overall 2.8) -- correctness=4.0, safety=4.0, style=3.0, tests=1.0, complexity=2.0
  • nvidia/nemotron-3-super-120b-a12b: REWORK (overall 3.2) -- correctness=4.0, safety=4.0, style=3.0, tests=2.0, complexity=3.0
  • nvidia/llama-3.3-nemotron-super-49b-v1.5: APPROVE_WITH_NITS (overall 4.2) -- correctness=5.0, safety=5.0, style=4.0, tests=3.0, complexity=4.0
  • nvidia/nemotron-3-ultra-550b-a55b: APPROVE_WITH_NITS (overall 4.2) -- correctness=5.0, safety=5.0, style=4.0, tests=3.0, complexity=4.0

Engraphis reference

Council verdict persisted as mem_01KXJSVN7A6YQXKW4HK8RRTJ81 (workspace Coding-Dev-Tools). Also logged to security-council workspace as mem_01KXJSVN7T1DFB3PZF5BT34KD2 (auth/security PR).

Posted automatically by the council-gate PR review cron. Auth/security PRs are reviewed at risk_level=high.

@Coding-Dev-Tools Coding-Dev-Tools added the council-approved Council gate approved this PR (APPROVE / APPROVE_WITH_NITS) label Jul 15, 2026
@Coding-Dev-Tools Coding-Dev-Tools merged commit 6869da6 into main Jul 15, 2026
7 checks passed
@Coding-Dev-Tools Coding-Dev-Tools deleted the fix/connect-agent-panel-urls branch July 15, 2026 12:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

council-approved Council gate approved this PR (APPROVE / APPROVE_WITH_NITS)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant