Skip to content

Update stacklok/toolhive-studio to v0.35.0#875

Merged
danbarr merged 6 commits into
mainfrom
renovate/stacklok-toolhive-studio-0.x
May 15, 2026
Merged

Update stacklok/toolhive-studio to v0.35.0#875
danbarr merged 6 commits into
mainfrom
renovate/stacklok-toolhive-studio-0.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 15, 2026 •
edited by github-actions Bot
Loading

This PR contains the following updates:

Package Update Change
stacklok/toolhive-studio minor v0.34.0 → v0.35.0

After this PR opens, .github/workflows/upstream-release-docs.yml adds source-verified content edits for the new release. For stacklok/toolhive, the same workflow also syncs reference assets (CLI help, Swagger) and regenerates the CRD MDX pages.

Release Notes

stacklok/toolhive-studio (stacklok/toolhive-studio)

v0.35.0

Compare Source

What's Changed

New Contributors

Full Changelog: stacklok/toolhive-studio@v0.34.0...v0.35.0

Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Docs update for toolhive-studio v0.35.0

At a glance
Upstream stacklok/toolhive-studio v0.34.0 → v0.35.0
Hand-written changes 2 commit(s)
Reference assets unchanged
Gaps 0
Release contributors 3 auto-assigned (see sidebar)
Action required Spot-check skill-authored prose for accuracy

Summary of changes

Summary of changes

  • Updated docs/toolhive/guides-ui/playground.mdx to reflect that each
    thread now persists its own agent, model, MCP tool selection, and skill
    selection (toolhive-studio#2253).
  • Added a "Choose an agent for a thread" section to playground.mdx
    covering the ToolHive Assistant and Skill Engineer built-ins, custom
    agents, and the Manage agents page. Agents are no longer gated by a
    feature flag (toolhive-studio#2256).
  • Added a "Work with chat messages" section to playground.mdx covering
    the per-message Copy button (toolhive-studio#2235), Edit with
    both the idle and rewind-and-retry paths (toolhive-studio#2241), and
    queue-while-streaming (toolhive-studio#2246).
  • Added a "See per-message cost" section to playground.mdx for the
    models.dev-backed pricing display (toolhive-studio#2255).
  • Updated docs/toolhive/guides-ui/registry.mdx to document the new
    Refresh button shown on the registry page when a non-default
    registry is configured (toolhive-studio#2216).

Run cost

Session Turns Cost (USD)
Generation 111 $7.9014
Editorial review 30 $2.1019
Total 141 $10.0033
How this PR was built

Two Claude Opus sessions run per release: a generation pass
(upstream-release-docs skill, 6 phases) followed by a fresh-
context editorial pass (docs-review). Prettier/ESLint
auto-fixes are applied after.

Auto-synced paths — do not hand-edit these in review:

  • docs/toolhive/reference/cli/
  • docs/toolhive/reference/crds/
  • static/api-specs/

If a "Gaps needing human context" section is present above,
each entry includes a paste-ready Helper prompt for local
Claude a reviewer can use to resolve the gap.

@renovate
Update stacklok/toolhive-studio to v0.35.0
302a232 
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate Bot added the autogen-docs Pull requests generated by automated release workflows label May 15, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented May 15, 2026 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs-website Ready Ready Preview, Comment May 15, 2026 6:25pm

Request Review

@github-actions github-actions Bot marked this pull request as draft May 15, 2026 12:49
@claude
Copy link
Copy Markdown
Contributor

claude Bot commented May 15, 2026 •
edited
Loading

Claude finished @renovate[bot]'s task in 11m 50s —— View job

Upstream release docs: toolhive-studio v0.34.0 → v0.35.0

Ran the upstream-release-docs skill end-to-end. Source-verified doc edits pushed in commit e53fe6f.

  • Phase 1 — Discovery: categorized PRs (~12 feature PRs, ~30 deps/internal)
  • Phase 2 — Deep-dive: fetched PR bodies, verified behavior against source at the v0.35.0 tag
  • Phase 3 — Doc-impact map built (2 files affected)
  • Phase 4 — Edits applied to playground.mdx and registry.mdx
  • Phase 5 — ESLint clean, prettier clean, /docs-review run (one accuracy fix applied to the queue/error path)
  • Phase 6 — SUMMARY.md written and changes committed/pushed

What changed in the docs

Skipped (verified no doc-relevant impact)

Not done

  • npm run build could not run in the action sandbox because the MCP metadata plugin invokes the thv CLI, which isn't installed here. CI on the PR will exercise the full build.
    · Branch

@github-actions
Document UI playground and registry changes from studio v0.35.0
e53fe6f 
- Note per-thread persistence of agent/model/MCP tools/skills
- Add agents, message copy/edit/queue, and per-message cost sections
- Add custom-registry refresh button to registry guide
@claude
Copy link
Copy Markdown
Contributor

claude Bot commented May 15, 2026 •
edited
Loading

Claude finished @renovate[bot]'s task in 3m 46s —— View job

Editorial review — toolhive-studio v0.35.0 docs

  • Read changed files & form review baseline
  • Run /docs-review over the two files in commit e53fe6f
  • Apply actionable fixes
  • Run prettier/eslint
  • Commit & push (73b148d)

Summary

The new content tracks the upstream PRs accurately. A few clarity/concision issues were worth fixing — no factual claims were introduced or changed.

Primary issues fixed

  1. Tautology in the rewritten Customize tools tip — playground.mdx: "Playground tool selection only applies inside the playground" was circular. Replaced with "Playground tool selection applies only to the active thread" so the contrast with customize-tools (which spans all clients and threads) is the actual scope difference.
  2. Misleading models.dev link — playground.mdx: link text "models.dev" pointed at /api.json, which would dump raw JSON for a reader expecting the project homepage. Repointed to https://models.dev.

Secondary issues fixed

Issue Fix
playground.mdx — "Copy: copy the text…" word repetition Use "copies" for consistency with the descriptive style of the Edit bullet
registry.mdx — "on demand" and "without having to" bloat in the Refresh paragraph Tightened to "…without restarting ToolHive or reopening the page"

Skipped (not editorial issues)

  • The Copy/Edit list mixes imperative and third-person verbs across items, but each bullet reads clearly on its own — wholesale restructuring would be cosmetic
  • The h4 placement of "Queue a message while a response is streaming" under "Work with chat messages" is a defensible structural choice (composer behavior is adjacent to message actions)
  • The <PREVIEW> placeholder and 100 → 50 = 150 token-totals format quote real UI strings — verified by the previous session against source

Verification

  • npm run prettier:fix clean (playground.mdx reformatted)
  • npm run eslint clean
    · Branch

@github-actions
Apply editorial polish to v0.35.0 playground/registry edits
73b148d 
- Customize tools tip now contrasts thread scope, not playground scope
- Fix models.dev link to point at homepage, not raw API JSON
- Tighten Copy bullet and custom-registry Refresh paragraph
@github-actions github-actions Bot requested review from peppescg, reyortiz3 and samuv May 15, 2026 13:06
@github-actions github-actions Bot marked this pull request as ready for review May 15, 2026 13:06
@samuv
Copy link
Copy Markdown
Contributor

samuv commented May 15, 2026

@claude remove the part related to refresh in registry, that part is still WIP

@claude
Copy link
Copy Markdown
Contributor

claude Bot commented May 15, 2026 •
edited
Loading

Claude finished @samuv's task in 54s —— View job

Removed WIP refresh button section from registry docs

  • Read registry.mdx and identified the refresh-button paragraph
  • Removed the section (5 lines)
  • Committed and pushed to the PR branch (0aecf6b)

Removed the following paragraph from docs/toolhive/guides-ui/registry.mdx:

When you've configured a custom registry, a Refresh button appears in the page header. Click it to pull the latest registry metadata and server list without restarting ToolHive or reopening the page. The button is hidden for the built-in registry.

The playground.mdx edits from the earlier sessions are unchanged.
· Branch

@github-actions @samuv
Remove WIP refresh button section from registry docs
0aecf6b 
Co-authored-by: Samuele V <samuv@users.noreply.github.com>
@samuv
Copy link
Copy Markdown
Contributor

samuv commented May 15, 2026

@claude The Playground page in docs/toolhive/guides-ui/playground.mdx still
reads as "a place to test MCP servers", but with agents now GA in
v0.35.0 (#2256) that framing is outdated. The Playground is now a
general-purpose agent workspace: users pick (or build) an agent and
chat with it, optionally giving it MCP tools and skills. MCP testing
is one use case among many, not the headline.

Please revisit playground.mdx end-to-end instead of appending
sections to the old structure. Specifically:

  • Reframe the intro and overview so the Playground is described as a
    chat workspace for agents — built-in or custom — not an MCP test
    harness.
  • Position the built-in agents (ToolHive Assistant, Skill Engineer)
    as the default entry point, with a short note on what each is for.
  • Promote custom agents and the Manage agents page (create, edit,
    pick per thread) to a first-class section, not a footnote.
  • Keep MCP tools and skills as configurable inputs to a thread
    (per-thread selection, #2253), but downstream of "which agent am I
    talking to" in the page flow.
  • Fold the existing per-message sections (Copy #2235, Edit #2241,
    Queue-while-streaming #2246, Cost #2255) into the new structure
    rather than leaving them as standalone additions.

For context, pull all agent-related PRs from stacklok/toolhive-studio,
not just the v0.34.0...v0.35.0 range — agents shipped behind a feature
flag over several earlier releases and were flipped on for everyone in
#2256, so the full history matters for the rewrite. Relevant PRs in
this release: #2245, #2253, #2256, #2258.

@claude
Copy link
Copy Markdown
Contributor

claude Bot commented May 15, 2026 •
edited
Loading

Claude finished @samuv's task in 7m 59s —— View job

Reframed Playground page as agent workspace

  • Read current playground.mdx
  • Research agent-related PRs from stacklok/toolhive-studio
  • Draft new agent-first structure
  • Rewrite playground.mdx end-to-end
  • Run npm run prettier:fix and npm run eslint
  • Commit and push (308da6f)

Summary of the rewrite

The page is now structured around agents from the top down. MCP testing is one of several example workflows, not the headline.

New page title: Test MCP servers → Chat with AI agents. Description rewritten to match. The URL slug stays /playground, and the in-product term Playground is still used in the body.

New section order:

  1. Intro - playground as a chat workspace for built-in or custom agents; testing MCP servers framed as one workflow among many.
  2. Key capabilities - reordered to lead with agents and per-thread context; folded Copy/Edit/Queue into a single "Message actions" capability; added "Per-message cost" and "Attachments" as their own capabilities.
  3. Getting started - steps now flow agent-first: access → providers → start a thread → pick an agent → add MCP tools and skills → chat. The MCP-tools step is no longer step 3.
  4. Choose an agent for a thread - covers ToolHive Assistant, Skill Engineer, per-thread selection, and most-recent inheritance.
  5. Manage custom agents - promoted to its own h3 under the agent section instead of a trailing sentence.
  6. Configure MCP tools and skills for a thread - new section that groups both inputs under a single agent-downstream heading, with h3s for MCP tools (existing content + image + Customize-tools tip) and Skills (new, per-thread scope).
  7. Manage chat threads - unchanged content, just renamed (was "Manage playground threads"), moved below agent and tool configuration.
  8. Work with chat messages - now the home for Copy, Edit (idle and rewind-and-retry paths), Queue a message while a response is streaming, See per-message cost, and Attach files to a message. All previously standalone, now folded into one structure.
  9. Example workflows (new) - Manage MCP servers through conversation, Test MCP server functionality, Build and audit skills. The screenshot of a chat response with tool execution moved here.
  10. Recommended practices - retained, with the testing-workflow subsection dropped (its bullets were generic) and "Agents, servers, and tools" replacing the old "Server management" subsection with an extra bullet about reusable custom agents.
  11. Next steps / Related information / Troubleshooting - retained; Next steps now leads with the Skills section and Related information now links to Skills.

Caveats

  • Cross-release PR research: the trigger asked me to pull all agent-related PRs across earlier releases too, not just v0.34.0...v0.35.0. gh and curl network commands aren't pre-approved in this Claude-action sandbox, so I couldn't run that discovery sweep. I relied on the source-verified content already in playground.mdx from the prior session (which covered #2245, #2253, #2256, #2258), the framing in your trigger comment, and the existing facts in the file. If there are agent capabilities from earlier flagged releases that weren't documented yet, please flag them and I'll add them.
  • Skills per-thread selection is documented as parallel to MCP tools per #2253. I described it generically ("pick which installed skills the agent can use in this thread") because the previous session didn't include UI details beyond the per-thread persistence. Let me know if there's a specific affordance I should describe more precisely.
  • npm run build can't run in this sandbox (MCP metadata plugin needs thv). PR CI will exercise it.
    · Branch

@github-actions @samuv
Reframe Playground page as agent workspace
308da6f 
Restructure playground.mdx end-to-end so AI agents - not MCP server
testing - are the headline use case. Built-in agents (ToolHive
Assistant, Skill Engineer) and the Manage agents page are now first
class; MCP tools and skills are positioned as per-thread inputs
downstream of agent selection. MCP testing moves to one of several
example workflows.

Co-authored-by: Samuele V <samuv@users.noreply.github.com>
@danbarr @claude
Tighten Playground page and promote it in sidebar
0bf738d 
Editorial polish on the v0.35.0 rewrite:
- Collapse the seven Key capabilities h3s into a bulleted list so the
  ToC stops carrying one-line subsections.
- Fix the intro's spaced-hyphen parenthetical and trailing-preposition
  catch-all.
- Split step 3 in Getting started so "After that" no longer dangles.
- Drop the redundant rejected-file toast list and the self-explanatory
  composer-placeholder block.
- "Configure client configuration" -> "Set up client configuration"
  in Next steps.

Move the Playground page above CLI access in the ToolHive UI sidebar
now that it's a primary workspace, not a test harness.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@danbarr
Copy link
Copy Markdown
Collaborator

danbarr commented May 15, 2026

Pushed 0bf738d with editorial cleanup on top of the rewrite.

Tightening on playground.mdx

  • Key capabilities was rendering as seven one-line h3s, which polluted the ToC. Collapsed to a bulleted list under a single h2. Renamed two items inline: "Detailed interaction logs" became "Inline tool calls" (it's about inline visibility, not a log artifact), and "Per-thread context" became "Per-thread settings" (avoids overloading "context" in an LLM doc).
  • Dropped the intro's spaced-hyphen parenthetical and the trailing-preposition catch-all sentence.
  • Split step 3 in Getting started so "After that" no longer dangles.
  • Dropped the rejected-file toast block (three quoted strings that paraphrased the limits stated three paragraphs up) and the composer-placeholder block (pure UX self-disclosure, also misplaced under "Attach files").
  • "Configure client configuration" became "Set up client configuration" in Next steps.

Sidebar

Promoted Playground above CLI access in the ToolHive UI section. With agents GA, it reads more like a primary workspace than a test harness.

@danbarr danbarr merged commit 61ff156 into main May 15, 2026
5 checks passed
@danbarr danbarr deleted the renovate/stacklok-toolhive-studio-0.x branch May 15, 2026 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@samuv samuv samuv approved these changes

@danbarr danbarr danbarr approved these changes

@peppescg peppescg Awaiting requested review from peppescg

@reyortiz3 reyortiz3 Awaiting requested review from reyortiz3

Assignees

No one assigned

Labels

autogen-docs Pull requests generated by automated release workflows

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@samuv @danbarr