How to make sure that an agent will go to existing PS console instead of spawning new one? #44
-
|
Hello dear @yotsuda ! Since I am asking, then another question besides that in Subj. How do you think - is it realistic to make an agent to act as declared REPL-base language interpreter (such as Python, or Groovy, or Clojure and so on) if I have started REPL session in MCP invokes Powershell window ? 🤔 That way it could be even more powerfull as programming teacher! With best regards, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
@luchezarno thanks for the kind words! Answering in order: 1. Making the agent use an existing PS console instead of spawning a new onePowerShell.MCP is designed so that the AI owns multiple consoles and switches between them automatically. The key here is the 2. Making the agent drive a REPL started inside the PS consoleThis isn't possible with PowerShell.MCP's current architecture — commands run via But you can do exactly this with Your question changed splash's directionI want to be explicit about this: your question reshaped splash in two ways. splashshell already supported multiple shells, but I hadn't planned on language REPLs at all. Your framing — "what if the agent could drive a Python / Groovy / Clojure REPL the same way it drives a shell?" — made me realize the exact same machinery could host any interactive process, which is how the current 18-adapter setup (4 shells + 11 REPLs + 3 debuggers) came to be. From the same realization came the second change: the scope clearly no longer fit under the word "shell," so a few days ago I renamed the project from To install the new package: I'd love to hear what you think of it — especially how the Python or groovysh REPL sessions turn out for educational use! |
Beta Was this translation helpful? Give feedback.
@luchezarno thanks for the kind words! Answering in order:
1. Making the agent use an existing PS console instead of spawning a new one
PowerShell.MCP is designed so that the AI owns multiple consoles and switches between them automatically. The key here is the
reasonparameter onstart_console: when omitted, an existing standby console is reused; only when specified is a new console forcibly spawned. The LLM is also nudged via the tool description to "not pass a reason unless a separate console is actually needed," so extra consoles normally don't pile up. On top of that, consoles outlive their parent MCP process, so restarting Claude Code reconnects to existing consoles via console re-c…