The latest articles on DEV Community by Dmitry (@dkrupenya). https://dev.to/dkrupenya https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F742141%2F63eabdc1-c592-43bd-b53b-032bf9dd1fbd.png https://dev.to/dkrupenya en Dmitry Sun, 17 May 2026 08:53:02 +0000 https://dev.to/dkrupenya/a-tmux-sidecar-for-repeatable-claudecodex-workflows-4426 https://dev.to/dkrupenya/a-tmux-sidecar-for-repeatable-claudecodex-workflows-4426 <p>I realized that I keep repeating almost the same workflow in my daily programming with Codex/Claude and OpenSpec: </p> <p>create proposal → review → implement → review code → write tests → update specs → close proposal. </p> <p>The workflow in general is the same, but the prompts are slightly different each time and require task specific edits. </p> <p>So I have created an app: a simple tmux sidecar that lets you define a workflow, track its status, reuse prompts between runs, edit them when needed, and send them to a coding agent in another tmux pane. </p> <p>It is intentionally not a full automation/orchestration framework. The goal is to reduce prompt copy-pasting while keeping you in control of each step.</p> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8no7sdlyhdnj34p2sqr6.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8no7sdlyhdnj34p2sqr6.png" alt="claude-adjunct" width="800" height="391"></a></p> <p>Hope, it may makes your coding workflow a little easier, and I’d appreciate any feedback.</p> <p><a href="https://github.com/dkrupenya/claude-adjunct" rel="noopener noreferrer">GitHub link</a></p> showdev productivity ai tooling