docs: pippy as the landing spot for CLI dispatch and MCP install - #12
Open
ShahriarAhnaf wants to merge 2 commits into
Open
docs: pippy as the landing spot for CLI dispatch and MCP install#12ShahriarAhnaf wants to merge 2 commits into
ShahriarAhnaf wants to merge 2 commits into
Conversation
Both the Sim backend dispatch and an eventual unified MCP server's client-side install belong in this package, for the same reason it already installs the engines instead of asking a user to find them. Writing the direction down before the code exists.
…ing the other Renode and pyrite have genuinely different capabilities — the gdb_* control plane and multi-machine/CAN/radio scenarios don't exist on the Rust side — so the unified surface is a Sim(backend=...)-shaped front door, with each engine keeping its own tool implementation behind it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
pippy(thesimanticPyPI package) is the intended landingspot for two not-yet-built extensions of its existing role: the
Simbackend dispatch growing into the CLI, and the client-side install point
for a future unified MCP server (mirroring how it already installs the
simulation engines).
docs/unified-surface.mdfromREADME.md's backend sectionand
docs/session-api.md's "Why not MCP" section.No code changes — this documents direction discussed with the maintainer
before any implementation starts.
Test plan