April 16, 2026

TL;DR. Keep one Codex thread alive on a schedule so it filters Slack, Gmail, and PRs into "this changes what you should do" pings instead of noise.

Takeaways

• Better context compaction flips the old assumption — a thread's value can grow over time, so stop resetting recurring work into fresh chats.
• Architecture: one "teammate" main thread for orchestration + long-lived subagent threads for depth in each lane (PRs, inbox, calendar).
• Thread automations are interval triggers on an existing thread, so the prompt collapses to "keep an eye on this for me" — the context and your past corrections are already there.
• Goal isn't summaries, it's interruptions that change your next action; during launch week his thread watched merged PRs + a blocked migration and stayed quiet until something actually shifted.

TL;DR. Polish isn't decorative—it's the subliminal tax consumers pay attention to, and past a certain stage, getting it wrong is expensive.

Takeaways

• "Polish" feels mystical but it's really perception engineering: the iMac box you can't throw away, the iPhone's inertia scroll.
• Speed and affordability win early; details and perception dominate later—know which stage you're in.