Skip to content

Add weekly update for 2026-05-18#883

Merged
danbarr merged 7 commits into
mainfrom
weekly-updates-2026-05-18
May 19, 2026
Merged

Add weekly update for 2026-05-18#883
danbarr merged 7 commits into
mainfrom
weekly-updates-2026-05-18

Conversation

@Derek2Tu
Copy link
Copy Markdown
Contributor

Description

Adds the 2026-05-18 weekly update post for ToolHive Studio v0.35.0:

  • Agents are GA in the Playground. Agent mode is enabled for everyone; a built-in skill engineering agent can scaffold and test skills directly inside the Playground.
  • Studio talks to thv over a UNIX socket / Windows named pipe. No more localhost TCP port binding, no port conflicts, and the socket is scoped to the current user.
  • Playground quality-of-life. Per-thread model/MCP/skills context, edit-and-resend, per-message cost (via models.dev), message queuing while a response is streaming, one-click copy, and an agent-aware empty state.

Skips fixes, security overrides, and under-the-hood items per the editorial pattern of the past few weekly posts. Happy to fold them in if you'd like.

Type of change

  • Documentation update

Submitter checklist

Content and formatting

  • I have reviewed the content for technical accuracy
  • I have reviewed the content for spelling, grammar, and style

🤖 Generated with Claude Code

Cover ToolHive Studio v0.35.0: Agents in the Playground are GA with a
built-in skill engineering agent, Studio-thv communication moves to
UNIX sockets and named pipes, and the Playground gains per-thread
context, message editing, per-message cost, and message queuing.

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

vercel Bot commented May 18, 2026

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

Project Deployment Actions Updated (UTC)
docs-website Ready Ready Preview, Comment May 18, 2026 10:24pm

Request Review

Align with the Playground guide: use the documented "Skill Engineer"
name, add "agent" to the per-thread context bullet, drop the redundant
"Windows ... on Windows" wording, rework the copy / empty-state bullet
to avoid repetition, link Playground and skills-build guides, and
rename the third section to "More Playground improvements".

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Lead the Skills section with the "go from idea to working skill" flow
(numbered steps), reframe the transport change as "no more port
conflicts" with the user benefits up top, and recast Playground
improvements with outcome-first bullets (each thread keeps its own
stack, edit and resend, see per-message cost, queue follow-ups).
Update the page title and description to match.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Re-lead with Agents going GA: both built-in agents (ToolHive Assistant
and Skill Engineer) plus custom agents, with per-thread context folded
into the same section so the agent story is whole. Drop the standalone
"build skills" framing in the title; that workflow is now an example of
what an agent can do for you.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Rephrase the launch framing across the title, sidebar label, description,
intro, and Agents section so the post reads as a feature announcement
rather than a release milestone.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Replace "Studio" with "ToolHive Desktop UI" / "the Desktop UI" to match
the rest of the docs. Trim the page title to "Agents arrive in the
Playground" so the headline carries the announcement on its own.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Drop the "available to everyone" qualifier since the section body
already establishes that, and disambiguate "Playground" from any other
ToolHive context.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@danbarr danbarr merged commit 8a6a3f8 into main May 19, 2026
4 checks passed
@danbarr danbarr deleted the weekly-updates-2026-05-18 branch May 19, 2026 12:16
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