Du wirst angemeldet...

Bitte warte, während wir deine Anmeldung überprüfen

Artikel · Freitag, 5. Juni 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.

Von Marius BongartsTech27 Ausgaben
← Zur aktuellen Ausgabe
Ausgaben5 / 27
Über Nacht von KI aus öffentlichen Quellen erstellt, täglich aktualisiert.
Agentic Coding
Freitag, 5. Juni 2026
AI Agents - Agentic Coding

Context windows have a cliff, OpenViking thinks in files, ECC ships 63 agents

1 Min. Lesezeit

The 80% context cliff

Your context window isn't failing—you're just crossing the cliff too late.

A detailed breakdown confirms the 80/20 rule: stop complex multi-file work at 80% capacity and reserve the final 20% for lightweight edits [Source: ClaudeFast]. The /compact command compresses history while keeping session memory intact—use it after finishing a major feature or before switching modes. Your CLAUDE.md file persists across sessions automatically, so put architectural decisions there instead of re-explaining them every time. Regular compaction usually means your tasks need subdivision, not bigger windows.

Build the exit-before-80 habit now.

OpenViking context database

What if your agent's memory worked like a filesystem instead of a vector blob?

OpenViking is a new open-source context database that unifies memories, resources, and skills under a familiar directory paradigm [Source: GitHub]. Its tiered loading system (L0/L1/L2) pulls context on demand—Claude Code with OpenViking hit 80% accuracy on long-context QA while using 63% fewer tokens and cutting latency by 58%. Agents also get smarter over time through automatic session extraction that updates memory after each task. It supports OpenAI, Gemini, and local models via Ollama.

Worth a weekend experiment if token bills are climbing.

ECC plugin system

Someone packaged the orchestration stack you've been building manually.

ECC ships 63 specialized agents for delegation, 251 skills including TDD workflows and verification loops, and hooks across 8+ event types [Source: GitHub]. The practical moves: keep under 10 MCPs enabled, cap MAX_THINKING_TOKENS at 10,000, and use /clear between unrelated tasks for instant context resets. Switching to Sonnet for most work cuts costs by 60%. The continuous-learning module extracts patterns with confidence scoring so your agent improves between sessions. It works across Claude Code, Cursor, Codex, and Copilot.

This is the plugin collection to watch.

Quellen
Claude Code Context Window: Optimize Your Token Usage
Claude Code Context Window: Optimize Your Token Usage
6 hours ago ... The Mental Model: Active Working Memory · /compact and When to Use It · CLAUDE.md as Persistent Memory · Strategic Task Chunking · Context Recovery Techniques.
claudefa.st
KI-Zusammenfassung

Claude Code's context window functions as active working memory that degrades as conversations lengthen, causing inconsistent code, repeated questions, and lost architectural decisions. The 80/20 rule recommends stopping complex multi-file tasks like refactoring and debugging at 80% capacity, reserving the final 20% for lightweight single-file edits. The /compact slash command compresses conversation history while maintaining session memory, best used after completing major features or before switching work modes. Your CLAUDE.md file persists across sessions automatically and should contain only essential context that Claude needs every session, preserving architectural decisions explicitly when made. Task chunking with natural breakpoints—completing components before integration and finishing research before implementation—prevents context exhaustion more effectively than pushing Claude to limits. Context recovery techniques include referencing checkpoint notes, asking Claude to scan for established patterns, providing a brief architecture overview, and starting with isolated tasks before expanding scope. Monitor context usage through the status bar token percentage, the /context command for detailed breakdowns, or automated StatusLine alerts, with the practical insight that regular compaction usually signals tasks need further subdivision rather than larger context windows.

Quelle öffnen
OpenViking is an open-source context database designed ... - GitHub
OpenViking is an open-source context database designed ... - GitHub
22 hours ago ... OpenViking unifies the management of context (memory, resources, and skills) ... Claude Code auto-memory, 57.21%, 49.1s, 353,306,422. Claude Code + OpenViking ...
github.com
KI-Zusammenfassung

OpenViking is a context database specifically designed for AI Agents that addresses fragmentation and context management challenges. It unifies memories, resources, and skills using a filesystem paradigm instead of traditional vector storage, enabling developers to manage an Agent's context like local files. The system features tiered context loading (L0/L1/L2 layers) that reduces token consumption by loading information on demand, directory recursive retrieval that combines vector search with hierarchical navigation for improved accuracy, and visualized retrieval trajectories for observable debugging. Evaluation results show significant improvements: Claude Code with OpenViking achieved 80.32% accuracy on long-context QA with 58.45% lower latency and 63.2% fewer tokens compared to native memory; on multi-turn agent tasks it improved retail accuracy by 6.87 percentage points and airline accuracy by 11.87 percentage points; and on knowledge-base QA it reached 91% accuracy with minimal retrieval latency while using only 13.8% of LightRAG's indexing costs. OpenViking includes automatic session management that iteratively extracts and updates memories from task execution, allowing agents to become "smarter with use," and supports multiple VLM providers including OpenAI, Volcengine Doubao, OpenAI Codex, Kimi Coding, and GLM. Installation is straightforward via pip, with interactive setup wizards for configuration and local model management via Ollama, plus a VikingBot framework for building AI agent applications on top of the context database.

Quelle öffnen
affaan-m/ECC: The agent harness performance ... - GitHub
affaan-m/ECC: The agent harness performance ... - GitHub
13 hours ago ... The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, ...
github.com
KI-Zusammenfassung

The website content describes ECC (a comprehensive Claude Code plugin system), which is highly relevant to your interest in advanced AI agent work, context window management, and agentic coding practices. ECC provides production-ready memory optimization techniques including session-based context persistence through hooks, strategic compaction at logical task breakpoints rather than relying solely on auto-compaction, and SessionStart context capping (configurable via ECC_SESSION_START_MAX_CHARS). For context window efficiency, the system recommends keeping under 10 MCPs enabled and under 80 active tools, disabling unused servers via /mcp, and using the strategic-compact skill to suggest compaction after research phases before implementation starts. Token optimization involves switching to Sonnet model for most tasks (60% cost reduction), capping MAX_THINKING_TOKENS at 10,000, and using /clear between unrelated tasks for instant resets. The system includes continuous-learning-v2 with instinct-based pattern extraction and confidence scoring, and cross-harness support spanning Claude Code, Cursor, OpenCode, Codex, and GitHub Copilot. ECC ships 63 specialized agents for delegation, 251 skills including tdd-workflow and verification-loop patterns, and hooks for automation across 8+ event types, with agent delegation designed to reduce token consumption compared to longer context-in-hand approaches.

Quelle öffnen
Über Nacht zusammengestellt von MorningMail.aiZugestellt um 04:55