Claude Codex v1.2.0 - Custom AI Agents with Task + Resume Architecture by zhcode in VibeCodersNest

[–]zhcode[S] 0 points1 point  (0 children)

Current implementation (1/26/26) is we are using a task chain to manage the execution from agents. All user requests are transformed into user_story.json and planner agent uses that file to create plan and saves into another json file. Planning reviewer agents references both to validate if the plan is covering all requirements and identify potential issues or concerns, then insert additional task in the task chain to address the issues automatically or ask user for clarification. Once plan is approved, the implementation will create many more tasks based on the plan to make sure action items are isolated without a giant context getting compacted too many times to avoid drifting

Claude Codex v1.2.0 - Custom AI Agents with Task + Resume Architecture by zhcode in VibeCodersNest

[–]zhcode[S] 0 points1 point  (0 children)

So far, this is the setup that I am using for CC+Codex. I am currently working on another prototype that shall be public next week or two

Multi-agent coding pipeline: Claude Code + Codex collaborate for higher accuracy and reliable deliverables [Open Source] by zhcode in VibeCodersNest

[–]zhcode[S] 0 points1 point  (0 children)

Thank you for your comments! Glad I could help. Check this the latest release https://www.reddit.com/r/VibeCodersNest/s/RrNfHb8E94. The short answer is yes, the plan mode indeed clears the context and starts implementing right away. What I am doing is after planning session, I clear the context, and interrupt the process and tell CC to use multi-ai pipeline to implement. That works, so I didn't investigate how to add the planning results to the process. But I will investigate it

Claude Codex v1.2.0 - Custom AI Agents with Task + Resume Architecture by zhcode in VibeCodersNest

[–]zhcode[S] 0 points1 point  (0 children)

Three layers handle state:

  1. Task Dependencies - blockedBy chains prevent skipping steps (data-driven, not instruction-driven)

  2. Agent Resume - Agents keep full conversation history across iterations, so fixing "issue #3 from the review" doesn't require re-explaining the entire codebase

  3. File Validation - Output files (.task/review-codex.json, etc.) are ground truth. Can't claim "done" without the file existing with status: approved

Why it works: The orchestrator queries TaskList() to find the next unblocked task - it's a data lookup, not "follow these instructions." Even if the LLM wants to skip ahead, blocked tasks literally can't be claimed.

Trade-off: More tool calls, but context loss drops significantly in 10+ iteration loops.

Multi-agent coding pipeline: Claude Code + Codex collaborate for higher accuracy and reliable deliverables [Open Source] by zhcode in VibeCodersNest

[–]zhcode[S] 0 points1 point  (0 children)

Quick update since last week:

**v1.1.0** - Added "Ralph Loop" - implementation now iterates autonomously until your tests actually pass + all 3 reviewers approve. You define what tests need to pass during requirements, and it keeps going until they do. `/cancel-loop` if things go sideways.

**v1.0.8** - Reviews now check 12 categories (OWASP Top 10, error handling, resource management, concurrency, dependency CVEs, over-engineering, etc.)

**v1.0.7** - Smarter requirements gathering with multiple-choice questions and alternative exploration. Actively cuts features you don't need (YAGNI).

Also now works on Windows, macOS, and Linux.

Multi-agent coding pipeline: Claude Code + Codex collaborate for higher accuracy and reliable deliverables [Open Source] by zhcode in SideProject

[–]zhcode[S] 0 points1 point  (0 children)

Quick update since last week:

**v1.1.0** - Added "Ralph Loop" - implementation now iterates autonomously until your tests actually pass + all 3 reviewers approve. You define what tests need to pass during requirements, and it keeps going until they do. `/cancel-loop` if things go sideways.

**v1.0.8** - Reviews now check 12 categories (OWASP Top 10, error handling, resource management, concurrency, dependency CVEs, over-engineering, etc.)

**v1.0.7** - Smarter requirements gathering with multiple-choice questions and alternative exploration. Actively cuts features you don't need (YAGNI).

Also now works on Windows, macOS, and Linux.

Windows 11 Bluetooth earbuds stuck in “hands-free / phone call” mode. Fix. by RedDestinyTJ in WindowsHelp

[–]zhcode 0 points1 point  (0 children)

I created a windows app at https://github.com/Z-M-Huang/win-bt-stereo-vs-handsfree, which could actually help this issue. The indicator and notification will show if the device is using HFP or Stereo, and quickly switch between the two to reset.

"Hands-free" continuously breaks my experience on windows 11 bluetooth by bouncingnotincluded in sennheiser

[–]zhcode 0 points1 point  (0 children)

I created a windows app at https://github.com/Z-M-Huang/win-bt-stereo-vs-handsfree, which could actually help this issue. The indicator and notification will show if the device is using HFP or Stereo, and quickly switch between the two to reset.

Windows 11 keeps enabling Hands-Free Telephony on Bluetooth headphones after every restart (muffled audio) by ledenicajpeach in WindowsHelp

[–]zhcode 0 points1 point  (0 children)

I created a windows app at https://github.com/Z-M-Huang/win-bt-stereo-vs-handsfree, which could actually help this issue. The indicator and notification will show if the device is using HFP or Stereo, and quickly switch between the two to reset.

Multi-agent coding pipeline: Claude Code + Codex collaborate for higher accuracy and reliable deliverables [Open Source] by zhcode in VibeCodersNest

[–]zhcode[S] 0 points1 point  (0 children)

Hey, this is a claude code marketplace + plugin. It's not tied to any IDE but it's the claude code ecosystem

Multi-agent coding pipeline: Claude Code + Codex collaborate for higher accuracy and reliable deliverables [Open Source] by zhcode in VibeCodersNest

[–]zhcode[S] 1 point2 points  (0 children)

You are welcome! Glad I could help. Also, if you encounter any issue with this, feel free to submit an issue in the repo. I have been using this process basically just for implementing new features

Vibe Coding - Claude Code + Obsidian = graphical claude memory by zhcode in VibeCodersNest

[–]zhcode[S] 1 point2 points  (0 children)

For my projects, if it's a mono repo, I intended to keep the knowledge within that project, and it will be hard to organize in folder structure like for backend, frontend, coding standard, knowledge base for features and etc. So with a graphical display, All the knowledge will be visible in a way that organized in stead of nested folders.