③4 records
Tools & Agents
- Sep 18, 2026OpenClaw — OpenClaw made its updates atomic — the existing gateway is kept alive while an update is prepared, and on failure it rolls back to the last working configuration, so there is always an agent left to diagnose problems and self-repair (2026.9.1 → 2026.9.2). The change came from the diagnosis that, with thousands of configuration options, not every combination of user setups can be tested; as its design rationale, OpenClaw noted that developers have a separate coding agent to fix things, but for ordinary users that agent is their only means of automation. SourceIf agents are treated as always-on operational infrastructure, a failed update is not a problem with one feature but the loss of the means of recovery itself. A case of the principle of zero-downtime deployment coming down to personal agent runtimes.
- Sep 17, 2026Run-Ze Fan et al. (Zoom and others) — An empirical study of coding-agent harness design — it evaluated 176 harness configurations across 4 models. ① The smaller the token budget, the more decisive context management becomes, and its main effect is preventing overflow failures; ② combining rule-based removal with LLM summarization works best, while letting the agent recover removed content brings almost no gain; ③ planning improves accuracy for weak models but mainly cost for strong ones; ④ weak models benefit from predefined tool interfaces, but strong models do better on both performance and efficiency when given only bash (especially on terminal-centric tasks). Trajectory-level analysis explains each mechanism. SourceBacks "the stronger the model, the thinner the harness should be" with measurements across 176 configurations. It marks the point where design guidance for axis ⑤, loop and harness engineering, moves from rules of thumb to evidence.
- Sep 16, 2026Anthropic — Retired Cowork as a separate product and merged it into a single Claude — users no longer choose between chat and agent work, and Claude judges which capabilities are needed. At the same time, it added Claude Docs, which creates documents within the conversation, and Claude Slides, which creates slides that users can edit and present directly and export to PowerPoint/PDF, and integrated Claude Design into the conversation. Rolling out over several weeks across web, desktop and mobile, starting with Pro and Max and followed by Team and Free, with Enterprise admins given at least 30 days' notice. SourceThe stage of selling a separate "agent product" closed in less than a year. It reflects the judgment that agents are not a separate app but the default behavior of chat, and bringing deliverables (documents, slides) into the conversation is the form that judgment takes.
- Sep 16, 2026xAI — Added memory to Grok Build — at the end of each turn, it skims the work in the background and writes down the team's coding conventions, the reasons behind decisions and facts about project infrastructure in topic-specific Markdown files (testing.md, code-style.md, etc.), then reads the relevant topics first when starting related work. Workspace scope and global scope are kept separate; `/memory` opens it for viewing, and `/dream` organizes recent notes by topic. It does not record task state, tentative conclusions, secrets or anything already in the repository or docs, and instructions in the current conversation take priority over memory. SourceOne more design that keeps agent memory not in a vector store but in files people can read and edit — the direction in which the industry is converging on where the canonical copy of memory should live.