OpenHandsの費用可視化とCline MCP認証対応で見るOSSエージェント週次A weekly OSS coding-agent roundup highlights three meaningful updates: per-run…

Self-hosted and open-source coding agents keep maturing, and their progress increasingly shows up not in flashy new capabilities but in the operational details that determine whether teams can actually deploy them. A weekly roundup covering the window from August 4 to August 7, 2026, illustrates this: of seven items that saw activity, three were judged genuinely worth using. Those three—per-run cost visibility in OpenHands, a skills collection for feeding team conventions to agents, and Model Context Protocol (MCP) authentication support in the Cline desktop app—point to an ecosystem that is quietly hardening around cost control and secure tool integration.

The most prominent update comes from OpenHands, which released versions 1.11.0 and 1.12.0 on the same day. The change that stands out is the ability to see the cost of each individual run. Agentic coding tools call large language models repeatedly as they plan, edit, and verify code, and those token charges can climb quickly during long autonomous sessions. Because that spending has often been difficult to attribute at the level of a single task, per-run visibility gives operators a concrete way to understand where budget is going and to spot runs that behave unexpectedly. For teams weighing whether to self-host an agent rather than pay for a managed service, this kind of transparency is a practical prerequisite rather than a luxury.

The second item addresses a different operational problem: getting agents to follow a team's established conventions. The roundup highlights a collection of "skills" designed to feed team rules and conventions to an agent so that its output aligns with how a particular group already works. Coding standards, naming rules, and project-specific expectations are easy for human reviewers to enforce but hard for a general-purpose model to infer, and reusable skill definitions offer a repeatable way to inject that context. This reflects a broader industry pattern in which agents are increasingly configured through structured, shareable instruction sets rather than ad hoc prompts.

The third update concerns Cline, a widely used open-source coding agent, whose desktop application gained MCP authentication support. MCP, the Model Context Protocol, is an open standard for connecting AI assistants to external tools and data sources through a common interface, and it has become a central building block for extending what agents can do. Adding authentication to that connection matters because MCP servers frequently sit in front of sensitive systems—repositories, internal APIs, and databases—where unauthenticated access would be a security risk. Support for authenticated MCP connections in the desktop client appears to bring Cline closer to the requirements of organizations that need to gate which tools an agent may reach and under what credentials.

Taken together, the three updates share a theme. None is a headline-grabbing new model or a dramatic leap in autonomous capability; instead, each closes a gap that tends to block real adoption. Cost visibility answers the question of what an agent is spending, skills collections answer how it should behave, and MCP authentication answers what it is allowed to touch. These are the concerns that surface once experimentation gives way to sustained team use.

For readers less familiar with the players, some context helps. OpenHands and Cline are both open-source coding agents that can run locally or self-hosted, which appeals to teams wary of sending proprietary code to third-party services. MCP has gained traction across the agent tooling landscape as a shared way to plug in capabilities, and the steady addition of features such as authentication is part of how that standard moves from early adoption toward production readiness. The roundup itself accompanies a video walkthrough but is written so that the key points can be followed without watching it.

The pace here—seven items in a roughly four-day window, with three deemed worth the effort—also signals how quickly this segment is moving. The cadence of near-daily releases, exemplified by OpenHands shipping two versions on one day, suggests active development but is likely to demand that adopters keep close track of changes. For te