Skip to content

feat(desktop): render GitHub smart link chips + typing indicator popover - #280

Closed
tellaho wants to merge 6 commits into
mainfrom
feat/pr-smart-links
Closed

feat(desktop): render GitHub smart link chips + typing indicator popover#280
tellaho wants to merge 6 commits into
mainfrom
feat/pr-smart-links

Conversation

@tellaho

@tellaho tellaho commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

Summary

  • GitHub PR, issue, and commit URLs in messages are rendered as inline smart chips with distinct icons (GitPullRequest, CircleDot, GitCommitHorizontal)
  • Commit URLs display a 7-character short SHA (owner/repo@abc1234)
  • Chips copy the full URL on text selection
  • Agent typing indicator now shows a popover with runtime details and ACP log preview

Test plan

  • Send a message containing a GitHub PR URL → renders as chip with PR icon
  • Send a message containing a GitHub issue URL → renders as chip with issue icon
  • Send a message containing a GitHub commit URL → renders as chip with short SHA
  • Verify non-GitHub links still render as regular underlined links
  • Selecting chip text copies the full URL, not the label
  • Click typing indicator avatar → popover shows agent runtime info

🤖 Generated with Claude Code

tellaho and others added 6 commits April 8, 2026 14:06
GitHub pull request URLs are now displayed as compact inline chips
with a pull request icon and owner/repo#number label instead of
raw URLs, matching the style of @mention and #channel-link chips.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Verifies PR URLs render as inline chips with icon and owner/repo#number,
open in new tabs, and that non-PR GitHub links remain regular links.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The visible chip label (icon + owner/repo#number) is marked
user-select:none while a hidden zero-width span holds the full URL
for clipboard copy. Adds an e2e test verifying the DOM structure.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Extend smart link rendering to convert GitHub issue URLs (CircleDot icon)
and commit URLs (GitCommitHorizontal icon, 7-char short SHA) into inline
chips, matching the existing PR chip pattern.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Click the typing indicator when a bot is typing to see:
- Agent name, command, and model
- Live-ticking elapsed runtime from lastStartedAt
- Destructive 'Interrupt' button that calls stopManagedAgent

Human typers are unchanged — no popover shown.
Hooks (useManagedAgentsQuery, useStopManagedAgentMutation) live
inside TypingIndicatorRow — zero prop changes to ChannelPane.
Show last 10 lines of agent harness log in the typing indicator
popover, dark terminal style with 5s auto-refresh. Gives
observability into what the agent is doing before interrupting.
@tellaho tellaho changed the title feat(desktop): render GitHub PR links as smart chips feat(desktop): render GitHub smart link chips + typing indicator popover Apr 9, 2026
@tellaho tellaho closed this Apr 10, 2026
jeremylongshore added a commit to intent-solutions-io/buzz that referenced this pull request Jul 29, 2026
…econcile the blueprint ledger to prod-up (#11)

WHAT: Adds 000-docs/006-DR-STND-authoritative-naming-and-boundaries.md as the
canonical source of truth for every Buzz asset name and the boundary between
them (owner amendment 2026-07-29, FINAL). Reconciles the 001 blueprint
completion ledger to reality and pins asset names in Phases 6/7.

WHY: Two assets deliberately share the string "intent-ops-buzz" — a VPS host
and a GitHub repository — and early planning blurred the code fork, the
contribution/verification lab, and the live ops lane into one "Buzz repo".
Conflating planes is how prod creds leak into a PR runner or an untrusted fork
branch gets deployed. The owner amendment forbids building durable
architecture docs (the contributor-lab architecture) until this naming record
lands; this is Track B, ordered FIRST. Chose the fork 000-docs as its home
(over the not-yet-created lab repo) because Track B requires no new repo and
the record must land now to unblock Track C.

WHERE (architecture): the fork is the code plane; this record governs the
four-plane flow — code fork (submit upstream) → contributor-lab repository
(execute tests) → Intent Eval Platform (decide) → intent-os ops/buzz (record)
→ intent-ops-buzz production host (run). Two separate gates: contribution
(SUBMIT/HOLD/…) and deployment (ship/no_ship/…).

CHANGES:
- 006 (new): six-asset table, host-vs-repo disambiguation rule, four-plane
  flow diagram, two-gate table, cross-plane boundary rules.
- 001 ledger: E2 → staging live + backups/restore proven; E2d → prod host
  built+deployed+verified pre-cutover (PRs block#279 block#280); E3 → in-flight with the
  remaining BLOCKING go-live gates enumerated; adds an ELab (contributor lab)
  row; E9 plugin named intent-ops-buzz-plugin + marked DEFERRED.
- 001 phase tree: new Phase 6 (contributor-lab pointer, architecture graduates
  in Track C, not before); Phase 7 plugin repo name pinned.
- 000-INDEX: 006 registered.

VERIFIED: grep shows every intent-ops-buzz use disambiguated (production host
vs repository) or fully org-qualified; content is public-safe (no
hosts-as-addresses, IPs, keys, or member data). The contributor-lab holding
draft stays untracked (it graduates into the lab repo in Track C).

RISKS: none — additive-only IS-overlay docs; zero upstream-path edits.
UNFINISHED: Track C (build the intent-ops-buzz repository) and the remaining
Track A go-live gates.

Bead: buzz-aet

Co-authored-by: jeremylongshore <jeremylongshore@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant