Glean 拾遗
Recent picks

27picks · chronological

09-09

WebMCP: Give AI Agents Declared Tools Instead of a DOM to Scrape

WebMCP is an incubation-stage browser standard from the W3C Web Machine Learning Community Group, proposed by Google and Microsoft. Instead of scraping the DOM, a website registers its actions as structured tools with JSON Schema; an AI agent discovers them, calls them with typed arguments, and the page runs real JavaScript inside the user's already-open, authenticated tab. The author validates the pattern with a deployed demo, Career Copilot: it registers 13 WebMCP tools on a single page, and ChatGPT—which now supports WebMCP—used those tools in a real run, aggregating 75 live openings from GitLab, Stripe and Databricks, scoring 24 job descriptions, surfacing skill gaps, shortlisting 4 roles, then stopping for explicit human approval before submitting 3 applications. The post covers the minimal imperative API (one registerTool() call wrapping existing functions), the current Chrome 149 origin trial and flag, the call flow, and the trust model: same-origin restrictions, readOnlyHint / untrustedContentHint annotations, and human-in-the-loop confirmation for consequential actions. It also states limitations honestly: it is early, Chrome-first today, needs site adoption, and the security model is still maturing.

sreenathmenon.com · 25 min · Agents · AI Engineering · Mcp
08-23

Long-term memory for coding agents with cross-vendor handoffs

ai-memory is a Rust-based long-term memory service for coding agents, addressing context loss when switching between tools like Claude Code, Codex, or Command Code. It uses MCP configuration and lifecycle hooks to automatically capture prompts, tool calls, and session boundaries, then compiles a concise summary and handoff at session end. The wiki is stored as plain Markdown in a git repo—grep-able, Obsidian-friendly, and backup-friendly—with no vector database to maintain. Retrieval blends FTS5, entity-match RRF, and graph-neighbor ranking, with optional embeddings and an optional LLM for consolidation. Best for engineers juggling multiple AI coding agents who want project memory to persist across sessions and vendors.

github.com · 62 min · Agent Engineering · Ai-Memory · CLI
08-13

AI Coding Dictionary: A Vocabulary for Agent Engineering

AI Hero publishes an AI coding dictionary that condenses the working vocabulary of agent engineering into terse entries. Instead of merely defining terms, it draws the conceptual lines that matter in practice: parametric vs contextual knowledge, the stateless model vs the stateful harness, input/output/cache tokens, and handoff mechanisms like compaction and handoff artifacts. It also introduces a few useful distinctions of its own — progressive disclosure as a way to load context on demand, Spec and Ticket as the building blocks of multi-session work, and DX/AX as separate measures of how well an environment serves humans and agents. Each definition is kept to a sentence or two, making the dictionary a useful reference for engineers debugging context-window waste, permission modes, or agent memory. For teams standardizing on terms like MCP, AGENTS.md, or subagents, this is a solid shared glossary. The piece is a lead magnet for AI Hero's newsletter, so treat it as a reference rather than a deep investigation.

www.aihero.dev · 10 min · Agent Engineering · Agents · Context Engineering
08-10

Cloudflare OS: an open source agent workspace with capability-based governance

Cloudflare has open-sourced Cloudflare OS, the agent workspace it uses internally, to bring AI leverage beyond programmers. A workspace is grounded in company-curated context and skills, and starts each agent with zero access. Resources are exposed as typed bindings, while Gatekeepers—service-specific Workers—hold credentials, enforce policy, and log every observed resource. Sharing a dashboard does not become a way to leak an underlying table, because the platform re-checks the viewer against the observation log. Apps are full-stack Workers with their own SQLite state, and the same server methods are callable by both users and agents. Model routing and spend run through AI Gateway, so admins can set budgets and pick models per task. The code is on GitHub and deployable into a Cloudflare account, with a reference deployment included. Written for engineers working on agent infrastructure, access control, and internal development platforms.

blog.cloudflare.com · 16 min · Agent Infrastructure · AI Agents · Capability Security
08-10

Cloudflare OS: an AI workspace with per-user sandboxed apps

Cloudflare OS is an open-source AI productivity environment that Cloudflare built for its own workforce. It acts as an operating system for both company operations and AI workloads: instead of fixed document types, every file is a 'Gadget'—a private, sandboxed application that an agent can create, modify, and debug on the user's behalf. A capability-based security layer called Gatekeepers brokers access to external services, logging side effects and letting users approve queued actions in bulk later instead of blocking the agent mid-task. The entire platform runs on Cloudflare Workers and workerd, leveraging Durable Objects, Dynamic Workers, and Facets, and every Gadget has real-time multiplayer collaboration by default. Blueprints let users share the code of an app so others can spawn their own copies. It is early access but substantial, and a valuable reference for engineers exploring agent infrastructure, per-user app sandboxing, and edge-based AI tooling.

github.com · 23 min · Agent Architecture · AI Agents · Cloudflare
08-03

Improving token efficiency in GitHub Agentic Workflows

GitHub's team instrumented its own fleet of Agentic Workflows through an API proxy, emitting a normalized token-usage.jsonl per run and building two daily agentic workflows—a usage Auditor and an Optimizer—that read those logs, flag anomalies, and file concrete optimization issues. The biggest wins came from pruning unused MCP tool registrations (each request can carry 10–15KB of schema overhead), replacing GitHub MCP calls with deterministic GitHub CLI invocations, and moving fixed data-gathering into pre-agentic setup steps. To compare across models they define Effective Tokens: ET = m×(1.0×I + 0.1×C + 4.0×O) with model multipliers. Of 12 production workflows, nine received optimizer changes; measured reductions were 62% for Auto-Triage Issues (109 runs), 43% for Security Guard, and 59% for Smoke Claude. One workflow regressed 5% due to workload shift, and one misconfigured bash allowlist caused a 64-turn fallback loop. The post argues for episode- and portfolio-level efficiency analysis.

github.blog · 18 min · Agent Engineering · CLI · Cost Optimization
08-01

Run Claude, GPT & Grok in One Window: Higgsfield Supercomputer Prompt Guide

A Higgsfield-sponsored walkthrough of its Supercomputer product, which aggregates Claude, GPT, Gemini and Grok into one chat and claims to route each task to the best model. It lists three integration paths: web UI, a Claude connector via MCP at https://mcp.higgsfield.ai/mcp, and a CLI (@higgsfield/cli), plus 18 copy-paste prompts for building web apps, CRMs, UGC videos, scheduled tasks and multi-agent 'graph engineering' workflows. The free tier supposedly covers planning, research and drafts, charging only for final rendered output. No routing details, benchmarks or failure cases are provided, and the piece acknowledges sponsorship at the end. Useful as a prompt/feature tour for curious power users, not as technical documentation.

x.com · 20 min · Agents · Ai Tooling · CLI
07-31

AI Programming: Workflows, Tool Types, and Review Checklist

This article from Kimi positions AI programming as a code-centered workflow: instruction plus repository/runtime context, then generation with evidence. It categorizes tools into completion, assistant, agent, and review, and maps AI support across the SDLC. Benefits claimed include cross-file consistency, less context loss, reusable verification, and more time for engineering judgment. The second half is a product overview for Kimi Code, listing Plan mode, Skills, Hooks, MCP, and swarm mode. It closes with a practical four-point checklist before accepting AI-generated code: requirement scope, repository/security fit, independent evidence, and permission control. Useful as a framework for developers new to AI coding, but note that it is largely a launch piece, not a technical report.

www.kimi.com · 11 min · Agents · AI Engineering · Developer Tools
07-31

Official MCP server giving coding agents live Chrome DevTools control

chrome-devtools-mcp is the Chrome team's official Model Context Protocol server that lets coding agents drive a real Chrome browser. It exposes DevTools capabilities as 50+ MCP tools covering input automation, navigation, network inspection, performance tracing, heap snapshots, console debugging, screenshots, and more, and uses Puppeteer to reliably wait for actions to complete. Agents can also attach to an already-running Chrome to reuse session state. Built for engineers who want AI assistants to perform browser automation, frontend debugging, and performance analysis.

github.com · 46 min · Agents · Browser Automation · Developer Tools
07-25

AI Agent Engineering in Depth: From Principles to Production

An open-source book providing a comprehensive guide to AI Agent engineering, from fundamental principles to production practices. Written by Li Bojie, it follows the core formula 'Agent = LLM + Context + Tools' across 10 chapters, covering context engineering, memory, tool use, coding agents, evaluation, post-training, continuous evolution, multimodal, and multi-agent collaboration. Includes 92 hands-on experiments (70+ runnable) on MCP, RAG, RL, etc. Ideal for engineers and researchers building production AI agents.

github.com · 15 min · Agents · AI Engineering · Context Engineering
07-23

Turn any codebase into a queryable knowledge graph, built for AI coding assistants

Graphify is an open-source tool that transforms codebases, docs, PDFs, images, etc. into a queryable knowledge graph. It uses tree-sitter for local deterministic AST parsing to extract code relationships (calls, imports, inheritance) without any LLM calls. Non-code files are semantically extracted via your AI assistant's model. The output includes an interactive HTML visualization, CLI queries (query/path/explain), and an MCP server for team use. Every edge is tagged EXTRACTED or INFERRED, providing transparency. Ideal for engineers navigating large monorepos, tracing dependencies, or understanding architecture.

github.com · 59 min · AI Agents · Developer Tools · Knowledge Graph
07-22

Local-first code intelligence graph for AI coding tools

code-review-graph is a local-first code intelligence graph that parses codebases with Tree-sitter and provides precise context to AI coding tools via the MCP protocol. It solves the problem of AI assistants re-reading large amounts of tokens during code review by performing blast-radius analysis to output only affected files. Features include 30+ MCP tools, incremental updates (<2s), a risk-scored GitHub Action for PR reviews, and support for custom languages. Benchmarks show median token reduction of 82x. Ideal for developers using AI coding assistants and teams maintaining large monorepos.

github.com · 36 min · Ai Tooling · Code Analysis · Code Intelligence
07-22

Kimi Code CLI: Terminal AI Coding Agent for Next-Gen Agents

Kimi Code CLI is an AI coding agent that runs in your terminal. It reads and edits code, runs shell commands, searches files, fetches web pages, and autonomously decides next steps based on feedback. It ships as a single binary with millisecond startup, features a purpose-built TUI, supports video input, AI-native MCP configuration, a rich plugin ecosystem, subagents for parallel tasks, lifecycle hooks, and ACP integration with editors like Zed and JetBrains. Ideal for developers seeking a powerful, extensible AI coding companion.

github.com · 4 min · AI Agents · CLI · Developer Tools
07-03

Local-first, agentic design workspace with 22 CLI agents and 150+ brand systems

Open Design is a local-first, open-source alternative to Claude Design. It is agent-native, meaning it doesn't ship its own agent but works with 22 coding-agent CLIs (Claude Code, Codex, Cursor, Copilot, etc.) already on your PATH. Using MCP, the agents read DESIGN.md brand systems, skills, and plugins to generate prototypes, live dashboards, decks, images, videos, and HyperFrames. Exports to HTML, PDF, PPTX, MP4. Supports BYOK for any OpenAI-compatible endpoint. Ships 100+ skills, 150+ brand-grade design systems, and 261 plugins. Ideal for engineers and designers who want brand fidelity and local control.

github.com · 35 min · Agent Engineering · Design Tools · Developer Tools
06-30

Browser Automation CLI for AI Agents

agent-browser is a native Rust CLI designed for AI agents to automate browser interactions. It uses a client-daemon architecture where the Rust daemon directly communicates with Chrome via CDP, eliminating the Node.js dependency. The tool offers a comprehensive command set covering navigation, element interaction (via ref/CSS/XPath/text selectors), snapshots, screenshots, network interception, session management, and authentication state persistence. It includes built-in safety features like domain allowlists, action policies, and encrypted state storage. It is optimized for AI workflows with accessibility tree snapshots, annotated screenshots, and MCP server support, making it ideal for engineers building AI agents, automated testing, web scraping, or enabling LLMs to control browsers reliably.

github.com · 64 min · AI Agents · Browser Automation · CDP
06-26

ECC: Cross-Harness Agent Operating System for Claude Code, Cursor & Beyond

ECC is a comprehensive agent harness operating system designed to enhance multiple AI coding assistants including Claude Code, Cursor, Codex, OpenCode, and GitHub Copilot. It's not a standalone AI tool but a collection of 260+ skills, 67+ agents, persistent memory, continuous learning, cost optimization, and security auditing features. By providing unified rules, hooks, and MCP configurations across platforms, it addresses issues of inconsistent agent behavior, context loss, and inadequate security. Ideal for professional developers deeply using AI coding assistants and teams seeking standardized agent engineering practices.

github.com · 94 min · Agent Engineering · Claude Code · Context Engineering
06-26

Human in the /loop

The author shares a practical workflow for coding with AI agents: define a verifiable 'definition of done' (model eval score, QA pass, green tests, performance benchmark), wrap it in a loop for the agent to iterate autonomously, and get notified via Slack when a decision is needed or the task completes. Loops run in the cloud, not on the local machine. The author runs 3-5 long loops concurrently plus shorter tasks. For engineers looking to level up from one-shot agent interactions to long-running autonomous optimization tasks.

06-24

Loop Engineering: How One Loop Ships 259 PRs a Month

This article breaks down the engineering of AI-driven development loops, contrasting a single engineer shipping 259 PRs in a month with a runaway loop that burned $47,000. It dissects six essential components—state file, automation/scheduling commands (e.g., /loop, /schedule, /goal), git worktrees, skills, MCP connectors, and sub-agents (writer vs. checker)—with concrete configuration examples for both Claude Code and OpenAI Codex. The piece provides a brake configuration template (max_turns, max_budget_usd, scope, circuit_breaker), describes four failure modes, and offers low-cost starting strategies. Aimed at engineers building or evaluating AI agent workflows.

x.com · 12 min · Agent Engineering · Ai Tooling · Claude Code
06-23

How To Use Loop Engineering To Build A Self-Improving Quant Trading System

Written by a backend developer working on quant trading systems, this article argues for moving beyond manual prompt-and-wait workflows to building self-running loops. It dissects six universal components of production loops: automation hooks, skill files (SKILL.md), state files (STATE.md), a separate verifier agent, Git worktrees for isolation, and MCP-based connectors. The author then wires these around the five-stage quant trading cycle (data ingestion, signal generation, verification, execution, risk monitoring), with a feedback mechanism that writes lessons back into the skill file for continuous improvement. Targeted at engineers building AI-driven or automated systems, especially in finance.

x.com · 13 min · Agents · Claude Code · Loop Engineering
06-23

30 Core Agentic Engineering Concepts Every Developer Should Know

This article distills 20 foundational concepts in agentic engineering, covering building blocks (Agent loop, Think-Act-Observe, state, patterns), configuration (config files, workflow files, prompt caching, context rot), capability (MCP, live document retrieval, persistent memory), orchestration (subagents, agent loops), guardrails (sandboxing, permissions, hooks, prompt injection defense, pre-commit gates), and observability (tracing, metrics). The author argues that frameworks change but these underlying ideas persist; understanding them makes any new tool familiar. Includes concrete config examples and practical advice (e.g., keep config files under 100 lines, distinguish proxy metrics from outcome metrics).

x.com · 24 min · Agent Architecture · Agents · AI Engineering
06-22

How to Build an AI Second Brain With Claude and Obsidian That Gets Smarter Every Day (Full Guide)

A step-by-step guide to building a persistent 'second brain' using Claude and Obsidian, based on Andrej Karpathy's LLM Wiki pattern. Obsidian stores all notes as local plain text files, while Claude (via MCP protocol) reads, organizes, and links the entire vault. Key steps: install Claude Desktop (paid plan), install Obsidian with Local REST API plugin, connect via MCP, create a CLAUDE.md profile via interview, structure projects with Inputs/Process/Outputs/Feedback folders, build reusable skills, wire in live data (calendar, email), and set up autopilot scheduling. The author stresses ownership (plain text, vendor-independent) and security ('keys, not prompts'). Aimed at engineers and knowledge workers tired of context loss.

x.com · 11 min · Ai-Memory · Claude Code · Context Engineering
06-17

Persistent Memory Engine for AI: Auto-Extract, Update, and Forget Intelligently

Supermemory is a memory and context layer for AI. It automatically extracts facts from conversations, builds and maintains user profiles, resolves contradictions, and intelligently forgets expired information. Combining hybrid search (RAG + memory), document processing, and live connectors (Google Drive, GitHub, etc.) into one API, it gives AI agents instant, personalized context. With plugins for Claude Code, Cursor, and more, it targets both developers integrating memory into apps and users wanting persistent AI memory across tools.

github.com · 14 min · Agent-Memory · Ai-Memory · Cloudflare
06-16

A Local-First Context Compression Layer for AI Agents: Library, Proxy, and MCP in One Stack

Headroom is a local-first context compression layer built specifically for AI coding agents. It slashes token consumption by 60-95% by compressing tool outputs, logs, files, and RAG results before they reach the LLM, all while maintaining answer accuracy. Usable as a Python/TypeScript library, a transparent proxy, a CLI wrapper for popular agents, or an MCP server, it fits into existing workflows without friction. Internally, it combines JSON structure-aware compression, AST-based code minification, and a custom fine-tuned model, grounded by a novel CCR reversible compression system that guarantees original data is never lost. This tool is ideal for engineers who rely heavily on coding agents and want to cut API costs without altering their current toolchain.

github.com · 18 min · Agents · Ast-Minification · Context Engineering
06-16

The Context Compression Layer for AI Agents: 60–95% Fewer Tokens, Zero Accuracy Loss

Headroom is a local-first context compression layer for AI agents that slashes token usage from tool outputs, logs, files, and RAG chunks by 60–95% before they reach the LLM, with preserved accuracy. It offers library, proxy, MCP server, and agent wrapper modes, using a content router to select the best compressor for JSON, code, or prose. Reversible compression ensures originals are retrievable on demand. With cross-agent memory and `headroom learn` for mining failed sessions, it is ideal for engineers running coding agents daily and anyone seeking to slash LLM costs without changing their workflow.

github.com · 18 min · Agent Architecture · Ai-Memory · Context Engineering
06-14

Hermes Agent: A Self-Improving, Multi-Platform AI Agent Runtime

Hermes Agent is a self-improving AI agent framework with a closed learning loop. It creates skills from experience, manages persistent memory across sessions, and operates over Telegram, Discord, Slack, and CLI via a single gateway. Any LLM backend can be used without code changes, and it runs on a $5 VPS or serverless infrastructure with near-zero idle cost. Built‑in cron scheduling, subagent delegation, and batch trajectory generation make it suitable for engineers and researchers who need an autonomous agent that evolves with use.

github.com · 11 min · Agent-Memory · Agents · CLI
06-13

Claude Agents & Skills for Investment Banking, Research, PE, and Wealth Management

Anthropic's official reference implementation of Claude agents for financial services, offering 9 end-to-end workflow agents for investment banking, research, PE, and wealth management, along with 8 vertical skill packs and 12+ MCP data connectors. Everything is file-based (Markdown/YAML), installable as Cowork plugins or deployable via Managed Agents API. Designed for technical teams who need ready-made finance AI workflows while retaining full customization.

github.com · 19 min · Agents · Anthropic · Financial-Services
06-12

How an Anthropic seller rebuilt his team's workflows with Claude Code

Jared Sires, a former account executive at Anthropic with no coding experience, used Claude Code to build CLAFTS, a Gmail-integrated tool that drafts customer emails in his voice while pulling context from live product documentation. The tool saves 10-15 hours per week. He expanded this into a sales plugin with skills for daily briefs, recaps, and pipeline management, wired into Salesforce, Gong, and other systems via MCP servers. About 80% of Anthropic's sales org now uses the plugin. The piece illustrates how non-technical practitioners can leverage AI coding tools to eliminate technical barriers and deliver workflow-specific software.

claude.com · 9 min · Agent Architecture · AI Engineering · Claude Code