mide + mshell Workflow Role = Accidental Superpower Here’s a fun side effect of how mide and mshell Workflow roles work together. When you load mshell_expert.role as a system prompt in AI Chat, the LLM is instructed to wrap every piece of code in fenced code blocks — exactly the mshell Workflow pipeline format. So when you ask it to “write Rust code that draws sine and cosine in ASCII”, it does two things at once without being asked: Puts the Rust source into the editor via Generate Puts the same code as a workflow block into LLM Output — ready to run in edi Now you have two independent execution paths from a single prompt: ▶ Run button → mide compiles and runs the Rust file → result appears in the Output panel ⚙ edi button → loads the code from LLM Output → executes it as a mshell Workflow stage → result appears in the mshell VTE terminal Same code. Same sine wave. Two completely different runtimes — both work perfectly. This isn’t a bug. The role does exactly what it’s told. The LLM just happens to speak fluent mshell Workflow by default when the role is loaded — and mide is ready to run whatever comes out, in whatever way you prefer. Moral of the story: write your roles right, and the pipeline takes care of itself. 🎯
