repositories / smith

smith

There are many coding harnesses - but this one is fast

owned by admin

docs: mcp second frontend decided with rmcp, web entry spec-owned

a2a0e3ab9442d8877ce9144d34e1326448f996b4

Oliver Jan Krylow <oliver@bugabinga.net> · 2026-09-25 17:59 UTC

unsigned 1 parent

Changed files (1)

TO_DISCUSS.md

ready

@@ -21,8 +21,7 @@

## Frontends

-- smith-web: SSE skeleton first (std-only possible), websocket when live input and multi-viewer arrive — websocket forces the async runtime decision. Delivers SMH-SPEC-RMTF0001. Trigger: TUIR completion or earlier remote need.

-- smith-mcp: MCP is a UI for agents and humans; smith-as-MCP-server consumes smith-ui so plugin features translate naturally into MCP (progress notifications, resources, tools). Frontend, not adapter mode. Trigger: external-harness integration wanted.

+- smith-mcp: decided as the second smith-ui consumer crate (agents as UI audience; stdio client-spawned like smith rpc; no daemon needed). rmcp is the engine-grade dependency from the start — MCP authorization machinery (OAuth 2.1 resource server, dynamic client registration) is the hard-to-get-right part, not the plumbing. Trigger: second-frontend slice.

- ACP (Agent Client Protocol): editor-facing agent protocol; technical shape and smith layer unclear — likely a frontend sibling of smith-rpc and smith-mcp, but unverified. Deferred. Trigger: editor integration wanted.

(Daemon and fleet discussion lives in SMH-SPEC-RMTF0001 and SMH-SPEC-FLET0001.)