Cognee v1 Memory, GPT-5.6 Sol Preview, UI-to-Code Workflows — AI Daily Jun 26
468 messages · 76 active members
Overview
Topics
@Max_Bernstein shared Cognee v1, claiming 145% better long-context recall than Opus 4.8/GPT 5.5, a 100B-token effective context window, and 6.9x lower cost. It's positioned as a drop-in memory layer for existing agents, landing amid wider community talk that 'memory frameworks are the new JS frameworks' and ongoing frustration with context poisoning.
OpenAI teased GPT-5.6 Sol, drawing split reactions: some builders liked the personality-driven naming over anthropomorphized 'ask Claude' patterns, others wanted shipping over teasing. Skepticism centered on whether Sol will meaningfully beat competitors on benchmarks like terminal-bench.
@tvrxm sparked a long discussion on getting Codex to match designed UI screens 1:1 after burning tokens for ~5/10 fidelity. Recommendations included Gemini AI Studio, Claude Design, Google Stitch, and a lazycodex/stitch workflow. Consensus: build a design system with components, typography, and spacing rules instead of feeding raw images to the agent.
@samb69 hit the classic Hermes problem of /goal stopping at 20 turns despite a 600-turn cap; @samtome's fix was to extend the compact timeout, which worked 'surprisingly well.' @jcartu added that 1M-context users must cron their hindsight memory stack 3x/day for dedup and consolidation, since context poisoning silently broke his own runs before automation.
@realcrischico asked how to share skills, CLAUDE.md, and config across Codex and Claude — the answer: symlink ./.claude to ./.codex and use `@AGENTS.md` includes so each harness layers on a shared base. Meanwhile @jcartu is NVFP4-quanting a new Orinth model (Qwen 3.5 397b + vision stack) on his RTX 6000, noting Cerebras hits 750 tok/sec but ASIC memory limits constrain KV cache and context length.
Key Takeaways
- Cognee v1 claims 100B-token context and 145% better recall than Opus 4.8/GPT 5.5 as a drop-in memory layer — worth testing on existing agent stacks.
- Fix Hermes /goal stopping early by extending the compact timeout; the 600-turn cap is meaningless if compaction trips first. Cron hindsight memory dedup 3x daily on 1M-context runs.
- For pixel-perfect UI generation, build a real design system (components, typography, spacing) before feeding screens to Codex — raw screenshots top out around 5/10 fidelity.
- Symlink ./.claude to ./.codex and use `@AGENTS.md` includes in CLAUDE.md to share skills across both harnesses with harness-specific overrides.
- Seedance via BytePlus ($55 / 13M tokens ≈ 50 videos at 480p) is meaningfully cheaper than Kie's ~$1.40 per 15s clip for high-volume ad creative; Cerebras hits 750 tok/sec but validate KV-cache limits first.
Hot Threads
Getting Codex to match designed UI screens 1:1
Elon sabotaging OpenAI/Anthropic via Grok, SpaceX chips & orbital data centers
OpenAI previews GPT-5.6 Sol — reactions to naming and timing