Signing you in...

Please wait while we verify your authentication

Article · Thursday, September 24, 2026

Agentic Coding

Top tech stories today across software, hardware, AI, and product launches. Senior engineer audience — skip rumour churn and pre-announcement leaks. Lead with shipping-now stories and what changed for builders.

By Marius BongartsTech120 editions
← See today's latest
Editions
14 / 120
Generated by AI overnight from public sources, refreshed daily.
Agentic Coding
Thursday, September 24, 2026
AI Agents - Agentic Coding

CLI agent catalog hits 130+, context strategy debate heats up, Anthropic reveals speed secrets

1 min read

CLI Agent Directory

Your terminal just got a map of 130+ coding agents.

The awesome-cli-coding-agents repo now catalogs everything from open-source tools like Hermes Agent and OpenCode to orchestration platforms that run multiple agents in parallel [Source: GitHub]. You'll find context compression tools like Headroom claiming 15–95% token reduction, persistent memory systems for maintaining project state across sessions, and starter kits for approval gates before risky operations. The MCP integration section pairs nicely with your existing skills setup.

Worth browsing before your next AGENTS.md revision.

Context Window Strategy

More context isn't always better—and now there's a framework for deciding.

A detailed OpenAI community thread breaks down the dependency-chain approach: instead of dumping your whole codebase, you trace the specific path from UI component through service layer to database for whatever you're modifying [Source: OpenAI]. The consensus is that excessive context actively degrades response quality. RAG, code indexing, and repo maps that retrieve only relevant dependencies outperform comprehensive dumps every time.

Test it on your next large feature—your token budget will thank you.

Claude Speed Optimizations

Anthropic just explained why Claude feels faster lately.

Boris Cherny's Threads post teases an engineering blog covering the techniques behind recent claude.ai and Desktop app speed improvements [Source: Threads]. The full post promises implementation details you can apply to your own apps. For Claude Code users, faster responses mean tighter feedback loops during agentic sessions—especially noticeable when you're running extended autonomous turns.

Watch for the full blog post to drop.

Opus 5.5 Limit Guide

Your context budget finally has official documentation.

ClaudeLog published a comprehensive limits guide covering Opus 5.5's 1M token window, reset timing around 5-hour cycles, and the max-turns parameter for non-interactive agentic work [Source: ClaudeLog]. Key takeaway: avoid the final 20% of your context window for complex tasks due to performance degradation. The guide also walks through strategic model selection—reserving Opus for architecture while using Sonnet 5 for routine edits maximizes your allocation.

Bookmark it next to the model card from yesterday.

Sources
If you've noticed how fast claude.ai and the Desktop app have ...
If you've noticed how fast claude.ai and the Desktop app have ...
5 hours ago ... Eivind Kjosbakken shows how long-running Claude Code sessions help maximize throughput and efficiency. ... workflow, anthropic, claude code].
threads.com
bradAGI/awesome-cli-coding-agents - GitHub
bradAGI/awesome-cli-coding-agents - GitHub
23 hours ago ... Supports multiple LLM providers with automatic failover and efficient context management. ... context for agentic workflows. myc ⭐ 12 — Local task-and ...
github.com
AI Summary

A curated list of 130+ CLI coding agents and orchestration tools for AI-powered terminal workflows. The list covers terminal-native agents (open source like Hermes Agent, OpenCode, and Claw Code; closed source like Claude Code and Warp), orchestration platforms for running multiple agents in parallel (Orca, Multica, Paseo), and infrastructure tools for context management, sandboxing, and agent coordination. Key techniques highlighted include context compression via Headroom (reducing tokens 15–95%), persistent memory systems for maintaining project context across sessions, MCP (Model Context Protocol) integration for tool extensibility, skills and AGENTS.md for encoding best practices, and workflow frameworks for autonomous multi-agent loops with verification gates. For solo founders working with Claude and Cursor daily, relevant best practices include session managers that isolate work in git worktrees, durable memory layers to avoid context reset, skill optimization to reduce repeated prompting, and approval gates before risky operations—all implemented in projects like Omnigent, Concord MCP, and Harness Starter Kit.

Visit source
Claude Code Limits - ClaudeLog
Claude Code Limits - ClaudeLog
19 hours ago ... Regular use of /compact and fresh session starts for unrelated tasks help maintain optimal performance. ... Understanding Claude Code limits helps optimize ...
claudelog.com
AI Summary

Claude Opus 5.5 now features a 1M token context window, enabling developers to load entire codebases for comprehensive development sessions with minimal optimization overhead. Strategic model selection—reserving Opus for architecture planning and complex analysis while using Sonnet 5 for execution and routine edits—maximizes allocation efficiency. Key context management techniques include using the /compact command to reduce context size, batching related changes into focused sessions, and avoiding the final 20% of context windows for complex tasks due to performance degradation. Development workflows are optimized by timing intensive work around 5-hour reset cycles, breaking complex features into manageable phases, and leveraging built-in tools like /context (v1.0.86+) for debugging context issues. For agentic coding, Claude Code's max-turns parameter in non-interactive mode controls autonomous actions, with guidelines suggesting 40-200+ turns for sub-agent workflows. The Max 5x plan ($100/month) supports all-day development with generous Opus allocation, while the Max 20x plan ($200/month) provides unrestricted access suitable for parallel projects and team development scenarios.

Visit source
How Much Context Is Actually Useful When Working With a Large ...
How Much Context Is Actually Useful When Working With a Large ...
12 hours ago ... prompting, ai-coding, context-engineering · saurabhsingh915606 ... Best practices for cost-efficient, high-quality context management in long AI chats.
community.openai.com
AI Summary

When working with large codebases and AI coding assistants like Claude, the key challenge is determining how much context to provide. Rather than including all files, developers should focus on providing a dependency chain specific to the task: if modifying a feature, include the relevant Angular component, service, API layer, backend controller, business logic, and database interactions. Excessive context can reduce response quality, so a balanced approach using techniques like RAG, code indexing, or repository maps to retrieve only relevant dependencies is more effective than comprehensive context dumps. For enterprise applications, architectural understanding matters as much as code generation, making strategic context selection and dependency verification critical practices.

Visit source
Compiled overnight by MorningMail.aiDelivered at 04:55 AM