OpenHuman is an open-source agent harness designed as a personal AI super intelligence, featuring local-first memory through Markdown trees in SQLite and orchestration capabilities via checkpointed graphs. It functions as a brain that builds persistent context from various data sources like email and calendars, acting as both an orchestrator for multi-agent workflows and a deep researcher with built-in web search and media generation tools.
- Features "Memory Trees" stored locally in Markdown format to create a Karpathy-style Obsidian wiki.
- Provides end-to-end encrypted agent-to-agent messaging using the Signal protocol.
- Supports visual, trigger-driven workflows that can be proposed by an AI and reviewed on a canvas.
- Includes a "Privacy Mode" which ensures no inference data leaves the user's machine when toggled.
- Features "Memory Trees" stored locally in Markdown format to create a Karpathy-style Obsidian wiki.
- Provides end-to-end encrypted agent-to-agent messaging using the Signal protocol.
- Supports visual, trigger-driven workflows that can be proposed by an AI and reviewed on a canvas.
- Includes a "Privacy Mode" which ensures no inference data leaves the user's machine when toggled.
bex is an open-source, self-hostable PaaS that positions itself as an AI-native alternative to Render, letting developers push Git and receive a deployed URL on their own Kubernetes infrastructure. Coding agents operate as first-class users via MCP alongside the dashboard, CLI, REST, and GraphQL interfaces, all backed by a shared Go core. The platform uses a Kubernetes operator with Cluster API for machine provisioning, supports Render-style `render.yaml` Blueprints for declarative service definitions, and ships managed Postgres, Key Value, logs, metrics, autoscaling, custom domains with TLS, and SSH access.
- 471 stars, 50 forks, 9 contributors — including Claude, Cursor, and Copilot listed as named GitHub contributors
- Apache-2.0 licensed; explicitly marked "not ready for production workloads" (public alpha)
- Language split: Go 58.5%, TypeScript 32.9%, Shell 6.7%
- Internal "lego" Go workspace enforces a strict `operator → types ← backend` one-way dependency DAG
- Tracks Render compatibility via an evidence-backed "parity ledger" (ADR018) rather than marketing claims
- Local quickstart provisions a kind cluster + Cluster API with Docker-container machines as tenant nodes
- Includes an Expo mobile app for safe supervision workflows (App Store listing present)
- Commit history references agent-driven QA rounds (w4/w5/w6 workstreams) and live dashboard re-probes
- 471 stars, 50 forks, 9 contributors — including Claude, Cursor, and Copilot listed as named GitHub contributors
- Apache-2.0 licensed; explicitly marked "not ready for production workloads" (public alpha)
- Language split: Go 58.5%, TypeScript 32.9%, Shell 6.7%
- Internal "lego" Go workspace enforces a strict `operator → types ← backend` one-way dependency DAG
- Tracks Render compatibility via an evidence-backed "parity ledger" (ADR018) rather than marketing claims
- Local quickstart provisions a kind cluster + Cluster API with Docker-container machines as tenant nodes
- Includes an Expo mobile app for safe supervision workflows (App Store listing present)
- Commit history references agent-driven QA rounds (w4/w5/w6 workstreams) and live dashboard re-probes
Leela Kumili writes about DoorDash's Flux platform, which moved LLM-based coding agent workloads from developer laptops to cloud infrastructure, automating 130,000 engineering tasks in a single month and supporting over 25,000 automated code reviews per week. The platform was built after local execution hit limits on power, uptime, and security, and is organized around four primitives: Firecracker microVM sandboxes, an in-house MCP gateway, YAML-defined playbooks, and multiple invocation surfaces (Slack, GitHub, cron, CLI, conversational interfaces).
- Sandboxes achieve a 95th percentile SLO under 5 seconds for full setup, including microVM start, repo clone, build tool install, and agent harness configuration.
- Playbooks can mix agent-driven steps with deterministic code where predictable execution or validation is required.
- The Agent Gateway enforces scoped permissions and logs all agent activity for auditing and policy enforcement.
- DoorDash switched Slack integration from private channels to public threads so engineers could observe agent executions and see how other teams delegated work.
- Sandboxes achieve a 95th percentile SLO under 5 seconds for full setup, including microVM start, repo clone, build tool install, and agent harness configuration.
- Playbooks can mix agent-driven steps with deterministic code where predictable execution or validation is required.
- The Agent Gateway enforces scoped permissions and logs all agent activity for auditing and policy enforcement.
- DoorDash switched Slack integration from private channels to public threads so engineers could observe agent executions and see how other teams delegated work.
A curated collection of resources, patterns, and templates for building reliable scaffolding for agents. Harness engineering is the discipline of designing the systems surrounding an agent—such as context delivery, tool interfaces, planning artifacts, verification loops, memory systems, and sandboxes—that determine its success or failure on real tasks. This focus is on the harness rather than the model.
- Design primitives for loops, planning, and memory
- Reference implementations and tutorials
- Security, sandboxing, and permissions
- Evaluation, verification, and observability
- Task runners and orchestration
- Human-in-the-loop and production operations
- Design primitives for loops, planning, and memory
- Reference implementations and tutorials
- Security, sandboxing, and permissions
- Evaluation, verification, and observability
- Task runners and orchestration
- Human-in-the-loop and production operations
The article discusses how integrating Anthropic's Claude Code persistent memory into automation workflows creates more personalized and efficient processes. By using the Claude Code CLI within an automation layer rather than relying solely on standard API calls, users can leverage Auto Memory and CLAUDE.md files to provide deep project context without manual prompt bloating. This approach enables smarter code repository management, automated documentation updates that reflect actual implementation changes, and more intelligent homelab monitoring. The author also distinguishes these memory features from the Model Context Protocol (MCP), which is better suited for fetching frequently changing data from external tools like GitHub or Notion.
Key topics:
- Claude Code's persistent memory via Auto Memory and CLAUDE.md
- Advantages of CLI implementation over standard API calls in workflows
- Practical applications in code repositories, documentation, and homelab environments
- Comparison between project memory and Model Context Protocol (MCP)
Key topics:
- Claude Code's persistent memory via Auto Memory and CLAUDE.md
- Advantages of CLI implementation over standard API calls in workflows
- Practical applications in code repositories, documentation, and homelab environments
- Comparison between project memory and Model Context Protocol (MCP)
GitNexus is an advanced code intelligence engine designed to act as a "nervous system" for AI agents. By indexing entire codebases into a comprehensive knowledge graph, it maps dependencies, call chains, and execution flows, ensuring that tools like Cursor and Claude Code have deep architectural awareness. The platform offers two primary modes: a CLI with Model Context Protocol (MCP) support for seamless integration into developer workflows, and a browser-based Web UI for quick, serverless exploration via WebAssembly. Unlike traditional Graph RAG, GitNexus utilizes precomputed relational intelligence to provide high-confidence impact analysis, multi-file renames, and automated wiki generation, significantly reducing the risk of breaking changes during AI-driven development.
The Model Context Protocol (MCP) is becoming a key component in the agentic AI space, enabling models to interact with external tools and data. The project's 2026 roadmap focuses on addressing challenges for production deployment. Key priorities include improving scalability by evolving the transport and session model, clarifying agent communication and task lifecycle management, maturing governance structures for wider community contribution, and preparing for enterprise requirements like audit trails and authentication. The roadmap also highlights ongoing exploration of areas like event-driven updates and security.
Developers are replacing bloated MCP servers with Markdown skill files — cutting token costs by 100x. This article explores a two-layer architecture emerging in production AI systems, separating knowledge from execution. It details how skills (Markdown files) encode stable knowledge, while MCP servers handle runtime API interactions. The piece advocates for a layered approach to optimize context window usage, reduce costs, and improve agent reasoning by prioritizing knowledge representation in a version-controlled, accessible format.
This article discusses the latest developments in AI agents, including the launch of Perplexity Computer, the shift from 'vibe coding' to 'agentic engineering', the standardization efforts around AI agents, and OpenAI's new deal with the Pentagon after Anthropic was dropped.
* **Multi-Agent Desktops Expand:**
* Perplexity launches "Computer" – easy-use digital worker.
* Notion & Anthropic boost agent capabilities via plugins.
* **Agent Standards Emerge:**
* Anthropic releases "Agent Skills" repository (GitHub).
* OpenAI adopts similar architecture.
* Agentic AI Foundation forming for standardization.
* **Agentic Engineering Takes Hold:**
* Karpathy: "Vibe coding" outdated.
* Focus shifts to code understanding & agent steering.
* **Cloudflare Optimizes for Agents:**
* "Markdown for Agents" reduces token usage on webpages.
* No website owner code changes needed.
* **Pentagon Shifts AI Partners:**
* Pentagon stops using Anthropic products (values concerns).
* OpenAI wins Pentagon deal – stipulations on surveillance/weapons.
* Potentially weaker safeguards than Anthropic.
* **Multi-Agent Desktops Expand:**
* Perplexity launches "Computer" – easy-use digital worker.
* Notion & Anthropic boost agent capabilities via plugins.
* **Agent Standards Emerge:**
* Anthropic releases "Agent Skills" repository (GitHub).
* OpenAI adopts similar architecture.
* Agentic AI Foundation forming for standardization.
* **Agentic Engineering Takes Hold:**
* Karpathy: "Vibe coding" outdated.
* Focus shifts to code understanding & agent steering.
* **Cloudflare Optimizes for Agents:**
* "Markdown for Agents" reduces token usage on webpages.
* No website owner code changes needed.
* **Pentagon Shifts AI Partners:**
* Pentagon stops using Anthropic products (values concerns).
* OpenAI wins Pentagon deal – stipulations on surveillance/weapons.
* Potentially weaker safeguards than Anthropic.
This article explains the differences between Model Context Protocol (MCP), Retrieval-Augmented Generation (RAG), and AI Agents, highlighting that they solve different problems at different layers of the AI stack. It also covers how ChatGPT routes prompts and handles modes, agent skills, architectural concepts for developers, and service deployment strategies.
