Open Pstack - keep Codex or Claude Code in charge while Devin implements a feature

If you use more than one coding subscription for a side project, Open Pstack lets you assign different parts of the work to different providers without moving the whole task out of Codex or Claude Code. I'm Arjit, and I maintain this free, MIT-licensed distribution: https://github.com/arjitj2/open-pstack . It builds on Lauren Tan's Pstack and the earlier ports by Michael Denyer and Eric Litman. For example, suppose your app needs saved search filters. Keep Codex as the parent, ask setup to assign implementation to devin:swe-2@high, and choose Claude for review. The parent coordinates the change; a Devin CLI worker implements it in a separate Git worktree. Each provider uses its own authenticated CLI and access. Exploration can use a separate role assignment too. The setup is to install the plugin, install Bun and the selected provider CLIs, then run pstack:setup-pstack to check model access and approve the assignments. Invoke pstack:poteto-mode with the feature request. For verification, pstack:create-verification-skill can create a project-specific map of real features and how to exercise them. For saved filters, a useful check would be saving a filter, reopening the app, and confirming it still produces the expected results. That is an example check, not a claimed demo result. Devin's current promotion makes the implementation role worth looking at: its pricing page lists Pro at $20/month with free SWE-2 use in Desktop and CLI through October 16, 2026, checked October 1: https://devin.ai/pricing Your Codex or Claude parent still has its own subscription and usage limits. External workers also don't inherit its MCP connections. This setup is useful when you want to choose the implementer and reviewer separately while keeping the parent responsible for checking the finished change.