Not sure if any of this is a good idea or not, but here's my "stack" for AI-assisted SaaS building: 1/ I use both the Claude Code and Codex native apps. I like both for slightly different reasons. In particular, Codex's preview browser with annotation markup is really helpful. 2/ also have CC and Codex installed on a remote VPS with a hand-off skill to hand off tasks from desktop app to VPS as needed. 3/ I use Fable primarily to orchestrate larger feature builds. It's set up to delegate coding tasks to Codex or Opus/Sonnet agents as needed and then reviews and iterates. Really big features start with it building a clickable mockup for me to approve. 4/ smaller, more direct tasks, bug fixes, etc., usually directly in Codex using 5.6 Sol. 5/ PRs get batched into a review queue, and then Fable reviews in a batch, runs tests, CI, and deploys to a staging environment. 6/ full manual browser QA in staging before release. I'll often have the agent compile a PDF of screenshots of every step of the QA so I can check for any weird UI bugs. 7/ Once it's good on staging, promote staging to main. After every deploy, Fable is instructed to keep an eye out post-deploy for any immediate bugs, errors, or issues. 8/ I also have Hermes installed on a VPS and a post-deploy hook where Hermes does a non-destructive browser QA of the production app to look for any immediate issues. 9/ a scheduled Codex task checks Sentry multiple times per day for any new errors and has a triaging workflow to either immediately create PRs and add them to a monitoring queue. In the case of extremely urgent, problematic issues, it can push a PR hotfix to main and notify me immediately in Slack. This Codex session has its own internal dashboard, which is an HTML artifact that it keeps up to date with: recurring issues, what can be learned to improve testing , what it pushed, etc 10/ For example, it appropriately nudged me to upgrade our Hetzner server, which it pretty much handled for me. It has a recurring task to check the overall health of our servers and databases, ensure backups are running properly, do dry runs of the backup restore, make any recommendations based on usage and capacity 11/ our team has a Slack channel for reporting bugs and feature requests. Codex skill checks that Slack channel for me periodically and proactively investigates and creates PRs for me to review. It's scheduled to close the loop and reply back in Slack when things have been resolved or features have been added.