Build Hour: Valuemaxxing with GPT-5.6
Summary
The session provides a deep dive into 'Value Maxxing' with GPT-5.6, shifting focus from merely maximizing token usage to optimizing AI agents for concrete business outcomes and cost efficiency. Key strategies include selecting the optimal model (Sol, Terra, Luna) based on workload needs, implementing advanced API features like programmatic tool calling and prompt caching, and structuring agent workflows to minimize redundant context processing.
Key takeaways
-
Shift from Token Maxxing to Value Maxxing
2:30
Progress should be measured by the value generated (e.g., time saved, quality improved), not just the number of tokens consumed. This requires defining clear outcomes and measurable 'good' for AI agents (evals).
-
Model Selection Strategy
4:09
The GPT-3.5 family includes Sol (flagship/complex tasks), Terra (balanced intelligence/cost/latency), and Luna (high-volume, cost/latency sensitive) to optimize for specific workloads.
-
Optimizing Agent Workflows with Codex
5:28
For day-to-day coding, starting with `GPT-5.6 Soul` on medium reasoning is often sufficient. Developers can also trade tokens for time using Fast mode or utilize Chronicle to build task memory.
-
Advanced API Techniques (Harness Optimization)
6:51
Implement programmatic tool calling (using a JavaScript sandbox) and prompt caching to significantly reduce input token costs and processing time. Persistent reasoning and compaction also boost performance and cache efficiency.
Technical details
-
GPT-5.6 Model Reasoning Levels
605s
The model offers new reasoning modes: Max (fully takes the leash off) and Ultra (a mode on top of Max, designed to natively use subagents). Using these modes is highly token intensive and recommended only for complex, heavy-hitter use cases.
-
Programmatic Tool Calling
431s
This feature allows models to write code into a JavaScript sandbox rather than reasoning through logic. This saves tokens by moving computation out of the model's chain of thought and can save entire model turns.
-
Prompt Caching (KV Cache)
506s
Caching reusable parts of prompts (like system instructions or date information) drastically reduces input costs. The cache is most effective when context remains append-only; modifying tools or system prompts breaks the cache.
-
Subagent Orchestration
702s
When using subagents, they are given only the specific context needed for their task by the main agent, which is more efficient than providing the full chat context. The effectiveness of multi-layer delegation (e.g., Soul -> Terra -> Luna) can be lossy.
Mentioned resources
Channel & topics
Watch on YouTube · Back to latest
This independent, AI-assisted summary is provided for commentary and informational purposes. It may contain errors or omit important context. Please watch the original video for the creator's complete presentation. Video, thumbnail, and related copyrights belong to their respective owners.