English static mirror for SEO/GEO · AI-assisted translation · Read Chinese original

16 Hours a Day of Vibe Coding: A Fable 5 + GPT-5.6 Sol Collaborative Workflow with Claude Planning, GPT Reviewing, and Codex Goal Mode Executing Overnight

Forum topic · 小凯 · 2026-07-15

Summary

A post on zhichai.net analyzes a detailed workflow shared by prominent Chinese AI blogger Digital Life Kazk, who reports coding up to 16 hours a day using a three-stage AI collaboration pipeline: Claude Fable 5 produces initial plans, GPT-5.6 Sol (via Codex) reviews and catches critical errors such as isolation issues, and Codex's new Goal Mode executes long-running tasks autonomously—his longest run lasted 17 hours. The 14-step pipeline covers branching, development, automated testing, PR creation, CI verification, merging, deployment, and post-task cleanup, with a custom 'cleanliness.skill' keeping code, docs, rules, and agent memory in sync. Key engineering choices include a self-hosted Tencent Cloud CI server instead of GitHub-hosted runners, task-type routing, and a human parallel limit of 6-7 tasks. The author's central claim: writing code is no longer the bottleneck in vibe coding—testing, verification, and plan review are. The post also weighs risks, including sustainability of 16-hour days, token costs of long agent runs, unreported failure rates of Goal Mode, and the non-open-sourced skill, concluding that the next product opportunity lies in test infrastructure and task routing rather than better code generation.

16 Hours a Day of Vibe Coding: A Fable 5 + GPT-5.6 Sol Collaborative Workflow with Claude Planning, GPT Reviewing, and Codex Goal Mode Executing Overnight

This post discusses a widely shared article by Chinese AI blogger Digital Life Kazk (published July 15, 8 a.m.), describing what he considers the best AI development workflow of the Fable 5 + GPT-5.6 Sol era, built around 16 hours of daily vibe coding.

Key points

  • Author background: Digital Life Kazk, a top AI blogger and founder of AIHOT (aihot.virxact.com), which recently surpassed 500,000 monthly active users. After Claude Fable 5's return and GPT-5.6's launch, his coding time reached 16 hours/day, coding until 6-7 a.m. and continuing via UU remote desktop + Codex while commuting.
  • Three-step workflow:
  • 1. Claude Fable 5 researches and drafts the plan (~20 minutes from a messy voice-input requirement). However, Fable 5's plans are not directly usable—the author notes the Claude family tends to "drop things" and be careless. 2. The requirement and Fable 5's plan are pasted into Codex with GPT-5.6 Sol (extra-high), framed as "a colleague's draft—review it thoroughly." GPT-5.6 Sol frequently finds serious problems; this time it took 6 minutes to find a critical isolation issue affecting other pipelines and the architecture. 3. Codex Goal Mode (via the plus button in the bottom-left) runs until the goal is met. His longest run: 17 hours, exhausting a full day's quota.
  • Full 14-step pipeline: agent verifies the problem → new branch/workspace → development → automated testing → push branch and create PR → CI acceptance → merge → deploy → verify in production → run a custom "cleanliness.skill" to sync code, docs, rules, and agent memory and review lessons → report to the author → await confirmation → clean up branches, workspaces, and temp databases → done.
  • Engineering configuration: test coverage kept in a "comfortable range"; a cheap Tencent Cloud server for CI instead of GitHub-hosted runners to save test/deploy time; task-type routing to balance test thoroughness and speed. Codex's 1.5x fast mode "isn't always faster" because deterministic test cycles dominate (5 minutes per submission, another 5 after each rejection).
  • Parallelism limit: 6-7 simultaneous tasks is his attention ceiling; beyond that he cannot personally review everything.
  • Core observations quoted from the author

    > "In vibe coding, development has been massively accelerated. Writing code is no longer the bottleneck—the bottleneck has moved to testing, verification, and your review of the plan."

    > "Most development skills like superpowers are basically useless now—believe me, nowhere near as good as this pipeline."

    > "The core is a dumbbell shape: on the left, the strongest model produces and refines the plan, then executes; on the right, your most important testing and research processes, plus cleanliness.skill keeping docs, rules, memory, and code unified."

    Analysis: three takeaways

    1. Claude/GPT division of labor, not rivalry: Fable 5 handles plan drafting and divergent thinking; GPT-5.6 Sol handles review, error-catching, and optimization. This two-stage collaboration is currently the most stable pattern. 2. Codex Goal Mode + long-horizon reliability is GPT-5.6 Sol's real moat: the author reports Goal Mode outperforms Claude Code because GPT's low hallucination rate and strong prompt adherence keep very long tasks from drifting, whereas Claude sometimes wanders or deadlocks. The post attributes this to intermediate checkpoint/re-anchoring mechanisms (inferred from the system card). 3. Test and deployment infrastructure is the real bottleneck: faster generation doesn't shorten end-to-end time when 5-minute deterministic test cycles dominate. The leverage is in CI infrastructure, task routing, and review capacity—production-grade agent engineering.

    The post also notes Kazk treats Codex as a full-stack product (Codex + ChatGPT Work + GPT-5.6 Sol), used on PC and via UU remote on the road—the first complete public validation of this layered strategy by a heavy user.

    Why it matters

  • The first complete heavy-user workflow since Fable 5's return, validating its production viability.
  • Goal Mode (run-until-goal, 17-hour continuous execution, automatic reporting) is a representative form for long-horizon agent tasks in 2026 H2; rivals like Claude Code's explicit sub-agents or Gemini CLI's short tasks lack equivalents.
  • "The bottleneck isn't writing code" is a validated but under-adopted judgment—the next product opportunity is likely test infrastructure and task routing, not better code generation.
  • One person running 6-7 parallel tasks at 16 h/day approximates a 5-7 person team's output, though this rests on a single public sample.
  • Risks and open questions

  • Sustainability of 16-hour days: the author calls it a coding addiction; long-term health costs are unknown.
  • Token economics: a 17-hour Goal Mode run likely consumes 5-10x the tokens of GPT-5.5; feasible for individuals, marginal for small teams, unsustainable for mid-size companies.
  • Failure modes: only successful 17-hour runs are public; real-world failure/rollback rates of Goal Mode are unreported.
  • cleanliness.skill portability: custom-built and not (yet) open-sourced, making the full workflow hard to replicate.
  • Fable 5 accessibility in China: 16 h/day usage likely relies on special channels or proxies.
  • Human review bandwidth: at 6-7 parallel tasks, agents may outpace human review, forcing "trust" over "audit"—the same boundary-of-autonomy problem raised by earlier full-access agent incidents.
Source: Digital Life Kazk WeChat official account (https://mp.weixin.qq.com/s/wm_LM83gyLM-auidBxprZw)

Tags

#vibe-coding#claude-fable-5#gpt-5-6-sol#codex-goal-mode#ai-agent-workflow#ci-infrastructure#multi-agent-parallelism#llm-collaboration

This page is an English static mirror generated for search and AI citation. It may be a full translation or structured summary of the Chinese original. Canonical interactive discussion lives on the Chinese page: https://zhichai.net/topic/178395166