Skip to content

feat(web): add dialectic reasoning playground#28

Merged
offendingcommit merged 1 commit into
mainfrom
feat/dialectic-playground
May 28, 2026
Merged

feat(web): add dialectic reasoning playground#28
offendingcommit merged 1 commit into
mainfrom
feat/dialectic-playground

Conversation

@offendingcommit
Copy link
Copy Markdown
Owner

Fans a single query across all five Honcho reasoning levels in parallel and shows the answers side by side with per-level latency — a tuning tool for picking a reasoning level.

  • components/playground/DialecticPlayground.tsx
  • Extends useChat() with an optional reasoning_level parameter (default unchanged)
  • New /workspaces/$workspaceId/peers/$peerId/playground route + a tab on PeerDetail
  • Unit tests + e2e screenshots

Credit

Cherry-picked from @BenSheridanEdwards's fork (feat/dialectic-playground), authorship preserved. Thanks Ben!

Verification

make check — lint + typecheck + tests pass locally.

Lets users fire one query at every Honcho reasoning level (minimal / low /
medium / high / max) in parallel and compare answers + latency side-by-side
in a 5-column grid.

- New route: /workspaces/:ws/peers/:peer/playground
- New component: DialecticPlayground with per-column state, level checkboxes
  to skip expensive levels, and a single Run button that fans out via
  Promise.all
- Extends useChat() to accept an optional reasoning_level parameter (was
  hardcoded to "low")
- Adds a Playground button next to Chat on the peer detail page
- Tests cover the parallel fan-out (peak concurrency = 5, no serial
  awaiting) and per-column latency measurement
- Screenshot Playwright spec (idle / mid-flight / settled) drives the
  images in docs/screenshots/ — regen with PLAYWRIGHT_BASE_URL=... pnpm
  exec playwright test e2e/playground.screenshots.spec.ts
@offendingcommit offendingcommit merged commit 0d86a96 into main May 28, 2026
2 checks passed
@offendingcommit offendingcommit deleted the feat/dialectic-playground branch May 28, 2026 19:32
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.

2 participants