Skip to content

Dgarson/tool schema descriptions#28

Closed
dgarson wants to merge 1 commit intodgarson/forkfrom
dgarson/tool-schema-descriptions
Closed

Dgarson/tool schema descriptions#28
dgarson wants to merge 1 commit intodgarson/forkfrom
dgarson/tool-schema-descriptions

Conversation

@dgarson
Copy link
Owner

@dgarson dgarson commented Feb 21, 2026

Summary

Describe the problem and fix in 2–5 bullets:

  • Problem:
  • Why it matters:
  • What changed:
  • What did NOT change (scope boundary):

Change Type (select all)

  • Bug fix
  • Feature
  • Refactor
  • Docs
  • Security hardening
  • Chore/infra

Scope (select all touched areas)

  • Gateway / orchestration
  • Skills / tool execution
  • Auth / tokens
  • Memory / storage
  • Integrations
  • API / contracts
  • UI / DX
  • CI/CD / infra

Linked Issue/PR

  • Closes #
  • Related #

User-visible / Behavior Changes

List user-visible changes (including defaults/config).
If none, write None.

Security Impact (required)

  • New permissions/capabilities? (Yes/No)
  • Secrets/tokens handling changed? (Yes/No)
  • New/changed network calls? (Yes/No)
  • Command/tool execution surface changed? (Yes/No)
  • Data access scope changed? (Yes/No)
  • If any Yes, explain risk + mitigation:

Repro + Verification

Environment

  • OS:
  • Runtime/container:
  • Model/provider:
  • Integration/channel (if any):
  • Relevant config (redacted):

Steps

Expected

Actual

Evidence

Attach at least one:

  • Failing test/log before + passing after
  • Trace/log snippets
  • Screenshot/recording
  • Perf numbers (if relevant)

Human Verification (required)

What you personally verified (not just CI), and how:

  • Verified scenarios:
  • Edge cases checked:
  • What you did not verify:

Compatibility / Migration

  • Backward compatible? (Yes/No)
  • Config/env changes? (Yes/No)
  • Migration needed? (Yes/No)
  • If yes, exact upgrade steps:

Failure Recovery (if this breaks)

  • How to disable/revert this change quickly:
  • Files/config to restore:
  • Known bad symptoms reviewers should watch for:

Risks and Mitigations

List only real risks for this PR. Add/remove entries as needed. If none, write None.

  • Risk:
    • Mitigation:

@dgarson dgarson changed the base branch from main to dgarson/fork February 21, 2026 22:37
@dgarson dgarson closed this Feb 22, 2026
dgarson added a commit that referenced this pull request Feb 22, 2026
Dedicated voice call UI for speaking directly to agents.

Features:
- Agent selector: Luis / Xavier / Stephan / Tim (with voice assignment, emoji, description)
- Large mic button with animated pulse rings — color changes by state
- 5 voice states: idle / connecting / listening / thinking / speaking
- State-appropriate mic icon: mic (idle), spinner (connecting), mic (listening), bouncing dots (thinking), speaker (speaking)
- Audio visualizer: 12-bar equalizer animating when active (indigo=listening, emerald=speaking)
- Session timer with red dot (●) when active
- Mute toggle, volume slider (0-100)
- Simulated conversation: connecting → listening → user transcript → thinking → agent response → back to listening
- Transcript panel (toggleable): user bubbles (indigo, right-aligned), agent bubbles (zinc, left-aligned), system events (centered pill)
- Transcript metadata: time, duration (s), STT confidence for low-confidence entries
- Live 'Listening…' indicator with pulse dot at transcript bottom
- Clear transcript button
- End Call button
- Seed conversation: 6 entries — realistic Horizon UI status exchange
- Full a11y: aria-pressed on mic/mute/transcript, aria-label, focus-visible rings

Build: ✓ 0 TS errors, 1.38s, 15.69 kB / gzip 4.76 kB
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