{
  "id": 6908979,
  "title": "I Kept a Shell Alias Just to Pipe stdin Into Workflows. 0.52.0 Retires It.",
  "url": "https://urgent.news/2026/09/12/i-kept-a-shell-alias-just-to-pipe-stdin-into-workflows-0-52-0-retires",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-12T10:07:57.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/donk8r/i-kept-a-shell-alias-just-to-pipe-stdin-into-workflows-0520-retires-it-22p"
  },
  "original_language": "en",
  "account": "Octomind's latest release, version 0.52.0, brings a significant change to how workflows are executed within the platform. The new release eliminates the need for a shell alias that allowed running a workflow in the background while typing within the session. With version 0.52.0, workflows are now integrated directly into the session, providing a more seamless experience.\n\nPreviously, users would use a shell alias, such as \"octomind workflow review --format jsonl notes.md\", to run a workflow mid-session while observing its progress in real-time. However, this workaround had its limitations. The context of the session, including the conversation with the agent, the state of the repository, and the purpose of the review, would be lost once the user left the session. This would force the user back to watching JSONL lines in the terminal, similar to being an external observer rather than an active participant.\n\nThe new release rectifies this issue by allowing users to run workflows directly within the session. The command structure is simplified, with everything after the workflow name being passed verbatim without any quoting rules or argument parsing. This means that the user can simply provide the input directly after the workflow name, ensuring that the workflow runs as intended without any ambiguity.\n\nOne of the standout features of this release is the ability to inspect a workflow before executing it. By simply calling a workflow with its name and no input, users can retrieve the definition of the workflow, including the steps involved and where the input is expected to be inserted. This feature provides users with a clear understanding of what the workflow entails, allowing them to make informed decisions before committing to it.\n\nThe release also introduces a few smaller enhancements. Spending-stop status is now accessible across sessions and via ACP requests, providing users with more visibility into their resource usage. Pending background jobs are reconciled and reported back once, ensuring that detached job evidence is preserved. Additionally, tool descriptions are billed only once per request, reducing token consumption.\n\nOverall, Octomind's version 0.52.0 release streamlines the workflow execution process, making it more intuitive and efficient for users. The integration of workflows directly into the session eliminates the need for workarounds and provides a more cohesive user experience. With this release, Octomind continues to enhance its platform, addressing user feedback and improving functionality to better serve its users.",
  "summary": "Workflows are my favorite part of Octomind. Multi-step, self-verifying jobs defined in TOML, shipped through taps — the built-in muvon/tap carries eighteen of them: review, develop, debug, deep-review, plan-and-build, research, content, and more. But there's one thing I kept doing that irritated me. To run a workflow mid-session, I left the session. Opened a terminal, piped input through stdin,…",
  "key_points": [
    "Octomind version 0.52.0 eliminates shell alias for background workflows",
    "Workflows now integrated directly into session for seamless experience",
    "Users can inspect workflows before execution to understand steps"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}