📝 SUMMARY This call delivered a full sweep of what our community does best: making sense of a fast-moving AI landscape and turning it into practical, working setups. With two major model releases dropping right before the sessions, the group compared early impressions and dug into what actually matters when evaluating models — efficiency per task, not just price. From there, members shared real projects in progress, from an open-source CRM and a resort venture to RAG apps and AI-native development thinking, followed by a deep dive into tooling architecture like meta-harnesses, personal memory layers, and multi-profile agent setups. The closing stretch covered hands-on workflow and security topics, including token budget management, voice-driven capture pipelines, and an important caution about chat-sharing privacy risks. Whether you missed it live or want a refresher, the takeaways below capture the ideas, tools, and lessons worth stealing for your own work. 💡 KEY INSIGHTS GPT-6 Sol is the price/quality workhorse — near Fable Low and Astra Low quality at half the price of prior 5.6 Sol. GPT-6 Luna is the smallest, cheapest model — about a quarter the price of Opus/Sol Low — ideal for high-volume tool-calling and operator tasks. Opus 5.5 is best for open-ended, loosely structured dev work; Sol/Luna win on cheaper, well-defined tasks. Ty Wells calls it "a leap, not a jump" over Opus 5. Opus 5.5 followed strict token-budget instructions well (built a site in ~3,000 tokens, though quality was poor); GPT-6 Sol ignored token limits and underperformed. The team now tracks "tokens per task completed" instead of raw token cost. Opus 5.5 inherited Fable 5's safety guardrails — sensitive security/biochem questions trigger a downgrade to Opus 4.8, with locked tracing logs. Anthropic is adding token refresh options on subscription plans, following OpenAI's lead. Claude "Projects" now works as a proper orchestrator for managing customer and project context. Enterprises running agentic apps on Bedrock face serious token budget issues — some burn millions monthly since cheaper models fail compliance needs, and enterprise billing is straight metered with no subscription flexibility.

AI Developer Accelerator — Coaching Call - September 22 VIEW RECORDING - 111 mins (No highlights) Meeting Purpose Review new AI models, developer tools, and ongoing projects. Key Takeaways - New Models Released: Opus 5.5 (strong coding), GPT-6 Sol (half-price workhorse), and GPT-6 Luna (fast, cheap tool-use). - T3 Code Adopted: The meta-harness for orchestrating multiple agents (Claude Code, Codex) is gaining adoption for its server-based isolation and mobile client. - Shared Memory Solved: Honcho.ai provides a cheap, LLM-curated vector store for persistent, cross-harness memory, addressing a key developer pain point. - Jev for Routing: Jev is emerging as a fast, cheap alternative to LLMs for model routing and real-time decision-making, enabling significant cost savings. Topics New Model Releases & Performance - Opus 5.5: A significant leap over Opus 5, now scoring higher than Fable. - Constraint Following: Shakur tested it by asking it to build a website and report token usage, which it did (3,000 tokens). - Limitation: Inherits Fable's safety guardrails, downgrading to Opus 4.8 for sensitive topics.

Last week, one agent ran autonomously for 17 hours building a website — and another member launched a platform that replaces $50k of subscriptions, live on the call. If you missed it, your agent stack is officially out of date. 😄 📞 HOW THE CALLS WORK The calls can run 2+ hours. We want to make sure we're respecting everyone's time. Especially those of you who actually show up. Here's the structure: 👉 Reply to this post with your questions before the call 👉 If you submit a question and you're on the call, you go first 👉 We work through questions in the order they came in 👉 Then we open it up for everyone else If you can't make the call but want your question answered, drop it in the comments. We'll get to it. But priority goes to people who are there. The goal is simple: if you're taking the time to show up, you shouldn't have to wait behind questions from people who aren't even on the call. There's plenty still in motion: Rod is running comparative benchmarks on GLM 5.3 vs. Claude, Juan's gearing up for his image-to-image venue outreach, and Lisa promised a report back on her harness evaluation (T3, Hermes, OpenRouter). If you've got follow-ups of your own — or questions sparked by last week's personal infrastructure round-robin — drop them below and we'll dig in. 🔗 ZOOM LINK (save this) https://us06web.zoom.us/j/81995207847?pwd=Xe6u6LmIQOmCP5VTnOwWYjDBfZNKGB.1 📅 WHEN Tuesday September 22nd at 6PM ET Looking forward to seeing you on the call!

📝 SUMMARY This week's call packed a lot into two hours: deep dives from Patrick Chouinard on his Beacon/Clara research pipeline, Astra-driven website rebuild, and skill-management philosophy; a business-growth discussion with Juan Torres on his AI photo booth; Rod Morrison's return with questions on operationalizing agent workflows; a live demo of Ty Wells' interactive pitch app for his Bahamas ERP/CRM platform; and an introduction from new member Lisa Jetton. The second half turned into a rich round-robin on personal infrastructure — Proxmox setups, T3 Code environments, multi-orchestrator stacks, and an open-source visual LLM project — plus updates from Ryan C and Morgan. Beyond the specifics, the recurring theme (voiced by Patrick near the end) was that the group itself serves as a weekly "context upgrade": a fast-moving AI landscape is impossible for any one person to track alone, and this community is how we keep up. If you missed it live, the recaps below are worth your time. 💡 KEY INSIGHTS Split your agent stack by concern: Patrick's "Beacon" does raw web research with zero personal context, then hands off to "Clara," which knows everything about him and turns it into a personalized morning briefing delivered via TTS/Discord. Archive everything your agents produce. Patrick keeps full transcripts + audio of every briefing so he can feed prior outputs back in and continuously improve — a self-optimizing loop. Let agents run autonomously with a clear role. Patrick had Astra (acting as "lead of a dev team") dispatch sub-agents and run ~17 hours on a website rebuild, only checking in when needed. Heavy agent building burns tokens fast — Patrick and Ty both blew through $200-tier subscriptions within a week. Budget for it. Turn your existing prompt templates into skills: decompose long templates into an "uber skill" that orchestrates sub-skills, add YAML frontmatter, and define which are callable vs slash commands. Keep a permanent, account-level tech stack definition so Claude and your agents stop recommending inconsistent tools and default to your approved stack.

AI Developer Accelerator — Coaching Call - September 15 VIEW RECORDING - 83 mins (No highlights) Meeting Purpose A weekly sync on AI projects, strategies, and development tools. Key Takeaways - Agentic Workflows Drive Efficiency: Custom agents (e.g., Patrick's "Beacon" news aggregator, Ty's "UI in reverse" code generator) are automating complex tasks, but this high-volume usage is rapidly consuming token limits. - Strategic Pivots for Revenue: Juan is shifting from development to sales for his AI photo booth, creating bespoke transformations for high-end venues to secure initial clients. - Operationalizing AI for Consulting: Rod is exploring a consulting product to help SMBs operationalize AI, focusing on creating custom skills and structured workflows to reduce token waste. - New Member Onboarding: Lisa, a full-stack engineer, joined to learn about agentic systems and is evaluating development harnesses like Hermes, T3 Stack, and PI. Topics Agentic Workflows & Token Management - Patrick's "Beacon" News Aggregator: - Workflow: "Beacon" (research agent) → raw report → "Clara" (contextualization agent) → TTS audio → internal archive (audio + transcript). - Goal: Create a continuous improvement loop by feeding user feedback from ChatGPT back into the system to refine future briefings.