AI Agent Monitoring

How to create a custom agent skill marketplace https://aikickstart.com.au/news/create-custom-agent-skill-marketplace https://aikickstart.com.au/news/create-custom-agent-skill-marketplace Build a marketplace where teams publish, find, and install agent skills, with versioning, ratings, search, and automated testing to gate quality. Fri, 19 Jun 2026 00:00:00 GMT How-to Guide daniel.fleuren@aikickstart.com.au (Daniel Fleuren) =1.2`, so installs stay predictable as skills evolve. # skill.yaml name: "database-query" version: "2.1.0" description: "Execute safe database queries with result formatting" author: "data-team@company.com" category: "data-access" tags: ["sql", "database", "analytics"] license: "MIT" requirements: runtime: "python3.11" memory_mb: 256 timeout_seconds: 30 dependencies: - "sql-parser>=1.2" - "result-formatter>=0.5" permissions: - "database:read" - "filesystem:tmp" inputs: query: type: "string" description: "SQL SELECT query" required: true format: type: "string" enum: ["json", "csv", "table"] default: "json" outputs: results: type: "array" description: "Query results" row_count: type: "integer" execution_time_ms: type: "integer" The `permissions` block matters more than it looks. Declaring `database:read` and `filesystem:tmp` up front means a reviewer can see a skill's blast radius before anyone runs it. Step 2: Marketplace API Now the server. This is the front door for publishing, searching, installing, and rating. The example below uses [FastAPI](https://fastapi.tiangolo.com/), though Express does the same job if your team lives in Node. Four endpoints carry the load. # marketplace/api.py from fastapi import FastAPI, UploadFile, File, HTTPException from pydantic import BaseModel from typing import List, Optional import hashlib import json app = FastAPI(title="Agent Skill Marketplace") class SkillMetadata(BaseModel): name: str version: str description: str author: str category: str tags: List[str] downloads: int = 0 rating: float = 0.0 review_count: int = 0 # In-memory store (use PostgreSQL in production) skill_registry = {} @app.post("/skills/publish") async def publish_skill( file: UploadFile = File(...), signature: Optional[str] = None ): """Publish a new skill to the marketplace.""" # Validate package contents = await file.read() # Verify structure try: manifest = extract_manifest(contents) except ValueError as e: raise HTTPException(400, f"Invalid package: {e}") # Run automated tests test_results = await run_skill_tests(contents) if test_results["pass_rate"] < 0.8: raise HTTPException(400, f"Tests failed: {test_results['details']}") # Store skill_id = f"{manifest['name']}@{manifest['version']}" skill_registry[skill_id] = { "metadata": manifest, "package_hash": hashlib.sha256(contents).hexdigest(), "package": contents, "test_results": test_results, "published_at": datetime.utcnow().isoformat() } return {"skill_id": skill_id, "status": "published", "tests": test_results} @app.get("/skills/search") async def search_skills( query: Optional[str] = None, category: Optional[str] = None, tags: Optional[List[str]] = None, sort_by: str = "relevance" ): """Search for skills with filtering.""" results = list(skill_registry.values()) if query: results = [r for r in results if query.lower() in r["metadata"]["name"].lower() or query.lower() in r["metadata"]["description"].lower()] if category: results = [r for r in results if r["metadata"]["category"] == category] if tags: results = [r for r in results if any(t in r["metadata"]["tags"] for t in tags)] if sort_by == "downloads": results.sort(key=lambda x: x["metadata"]["downloads"], reverse=True) elif sort_by == "rating": results.sort(key=lambda x: x["metadata"]["rating"], reverse=True) return {"results": [r["metadata"] for r in results], "total": len(results)} @app.post("/skills/{skill_id}/install") async def install_skill(skill_id: str, tenant: str): """Install a skill for a tenant.""" if skill_id not in skill_registry: raise HTTPException(404, "Skill not found") skill = skill_registry[skill_id] # Record installation skill["metadata"]["downloads"] += 1 return { "skill": skill["metadata"], "package_hash": skill["package_hash"], "install_script": generate_install_script(skill) } @app.post("/skills/{skill_id}/rate") async def rate_skill(skill_id: str, rating: int, review: Optional[str] = None): """Rate and review a skill.""" if skill_id not in skill_registry: raise HTTPException(404, "Skill not found") if not 1 <= rating <= 5: raise HTTPException(400, "Rating must be 1-5") skill = skill_registry[skill_id] current = skill["metadata"] # Update running average new_count = current["review_count"] + 1 new_rating = (current["rating"] * current["review_count"] + rating) / new_count current["rating"] = round(new_rating, 2) current["review_count"] = new_count return {"rating": current["rating"], "review_count": new_count} Two things to call out. The publish endpoint refuses anything that scores below an 80% pass rate, so a broken skill never lands in the catalogue. And the rate endpoint keeps a running average rather than recomputing from stored reviews, cheap, and good enough for ranking. Swap the in-memory `skill_registry` for PostgreSQL before this leaves your laptop; the dictionary is there to make the logic readable, not to survive a restart. Step 3: Automated Testing This is the part that earns trust. Before a skill is published, its tests run inside a throwaway container, never on the host, using the official [Docker SDK for Python](https://docker-py.readthedocs.io/). Memory is capped, a timeout is enforced, and the package is mounted read-only. If the suite passes, the skill is allowed through. If it fails or the container blows up, the publish is rejected and the author sees why. # marketplace/testing.py import docker import tempfile import os from pathlib import Path class SkillTestRunner: def __init__(self): self.docker = docker.from_env() async def run_tests(self, package_bytes: bytes) -> dict: with tempfile.TemporaryDirectory() as tmpdir: # Extract package extract_package(package_bytes, tmpdir) manifest_path = Path(tmpdir) / "skill.yaml" with open(manifest_path) as f: manifest = yaml.safe_load(f) # Run tests in sandboxed container try: container = self.docker.containers.run( image=f"python:{manifest['requirements']['runtime']}-slim", command="python -m pytest tests/ -v --json-report", volumes={tmpdir: {"bind": "/skill", "mode": "ro"}}, working_dir="/skill", mem_limit="256m", timeout=60, detach=True ) result = container.wait(timeout=60) logs = container.logs().decode() container.remove() return { "pass_rate": 1.0 if result["StatusCode"] == 0 else 0.0, "exit_code": result["StatusCode"], "logs": logs, "details": parse_test_results(logs) } except Exception as e: return { "pass_rate": 0.0, "error": str(e), "details": [] } def validate_manifest(self, manifest: dict) -> list[str]: """Validate skill manifest. Returns list of errors.""" errors = [] required = ["name", "version", "description", "author", "category"] for field in required: if field not in manifest: errors.append(f"Missing required field: {field}") if "permissions" in manifest: for perm in manifest["permissions"]: if not is_valid_permission(perm): errors.append(f"Invalid permission: {perm}") return errors One caveat if you copy this directly: the example interpolates `requirements.runtime` straight into the image tag, which produces `python:python3.11-slim`, not a real tag. Store the bare version (`3.11`) in the manifest, or strip the `python` prefix before you build the tag. It's a small fix, but it'll stop your first test run cold if you miss it. `validate_manifest` runs before any of that, catching missing fields and bogus permissions cheaply so you don't spin up a container just to learn the YAML was malformed. Step 4: CLI Install Command Last piece: the command a colleague actually types. This is where the whole system pays off, a skill someone else built, tested, and rated arrives in one line. The CLI uses [click](https://click.palletsprojects.com/), which keeps argument parsing and help text out of your way. # marketplace/cli.py import click import requests @click.group() def cli(): """Agent Skill Marketplace CLI""" pass @cli.command() @click.argument("skill_name") @click.option("--version", default="latest") @click.option("--registry", default="https://skills.company.com") def install(skill_name: str, version: str, registry: str): """Install a skill from the marketplace.""" skill_id = f"{skill_name}@{version}" click.echo(f"Installing {skill_id}...") response = requests.post(f"{registry}/skills/{skill_id}/install") if response.status_code != 200: click.echo(f"Error: {response.json()['detail']}", err=True) return data = response.json() # Download and extract download_and_install(data) click.echo(f"✓ {skill_name} installed successfully!") click.echo(f" Rating: {data['skill']['rating']}/5 ({data['skill']['review_count']} reviews)") @cli.command() @click.argument("query") @click.option("--category") @click.option("--sort", type=click.Choice(["relevance", "downloads", "rating"])) def search(query: str, category: Optional[str], sort: str): """Search for skills in the marketplace.""" response = requests.get( "https://skills.company.com/skills/search", params={"query": query, "category": category, "sort_by": sort} ) results = response.json()["results"] click.echo(f"Found {len(results)} skills: ") for skill in results: click.echo(f" {skill['name']} v{skill['version']}") click.echo(f" {skill['description']}") click.echo(f" ★ {skill['rating']} | ↓ {skill['downloads']} | {', '.join(skill['tags'][:3])}") click.echo() if __name__ == "__main__": cli() A note on the headline `claude skill install ` command from the Key Takeaways: treat that as the command for your own self-built marketplace, not as official Claude Code syntax. Claude Code itself ships skills inside plugins, and the real install command is `/plugin install @` in-app, or `claude plugin install @` from the CLI, see [Anthropic's plugin docs](https://code.claude.com/docs/en/discover-plugins) for the current syntax. If you're building the marketplace described here, name your CLI command whatever you like; just don't confuse it with the built-in one. Do/Don't: Require automated tests before publishing: Allow untested skills in the marketplace Version skills with semantic versioning: Use arbitrary version numbers Sandbox skill execution during testing: Run skill tests on the host machine Show ratings and review counts: Hide quality signals from users Support skill dependencies: Let skills depend on untrusted packages Conclusion: The payoff is simple: build a skill once, and every team gets it. The data team's query helper stops being a private snippet and becomes something finance installs in a line. Untested code never reaches a colleague, because the publish gate runs the tests first. And the catalogue grows on its own, because contributing is easier than rebuilding. That compounding, each team's work quietly available to the next, is what makes an agent platform worth more than the sum of its agents.]]> Claude Code Review: Is $100/mo Worth It for Teams? https://aikickstart.com.au/news/claude-code-review-2026 https://aikickstart.com.au/news/claude-code-review-2026 We tested Anthropic's premium team coding agent for 30 days. Here's whether Plan Mode, Hooks, and the Task System justify the price tag. Wed, 10 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Cursor IDE Review: The Best AI Coding Editor in 2026 https://aikickstart.com.au/news/cursor-ide-review-2026 https://aikickstart.com.au/news/cursor-ide-review-2026 Cursor has gone from VS Code fork to the default IDE for AI-assisted development. We break down what makes it special and what still needs work. Wed, 10 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) GitHub Copilot vs Claude Code: Which Coding Assistant Wins? https://aikickstart.com.au/news/github-copilot-vs-claude-code-2026 https://aikickstart.com.au/news/github-copilot-vs-claude-code-2026 The two titans of AI coding go head-to-head. We compared them on 12 dimensions across 4 weeks of real-world development. Here's the definitive verdict. Thu, 11 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Perplexity Pro Review: Real-Time Search That Actually Works https://aikickstart.com.au/news/perplexity-pro-review-2026 https://aikickstart.com.au/news/perplexity-pro-review-2026 Perplexity Pro combines GPT-5.5 with live web search. After 3 months of daily use, here's whether the $20/mo subscription delivers on its promises. Thu, 11 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) ChatGPT Plus Review: Still the Default Choice? https://aikickstart.com.au/news/chatgpt-plus-review-2026 https://aikickstart.com.au/news/chatgpt-plus-review-2026 With GPT-5.5 Instant as the default model, ChatGPT Plus remains the most versatile AI subscription. But is it still the best value at $20/mo? Fri, 12 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Replit Core Review: Agent Mode and Full-Stack Deployment https://aikickstart.com.au/news/replit-core-review-2026 https://aikickstart.com.au/news/replit-core-review-2026 Replit Core at $7/mo offers the cheapest entry point into AI-assisted coding. We tested Agent Mode, deployments, and the new full-stack features. Fri, 12 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Hugging Face Review: The Hub for Open-Source AI https://aikickstart.com.au/news/hugging-face-review-2026 https://aikickstart.com.au/news/hugging-face-review-2026 Hugging Face hosts 1.2 million models, 180k datasets, and the most active ML community on Earth. We tested the free tier and Pro subscription. Sat, 13 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Ollama Review: Run Any Model Locally https://aikickstart.com.au/news/ollama-review-2026 https://aikickstart.com.au/news/ollama-review-2026 Ollama makes running LLMs locally as easy as `docker run`. We tested 15 models across Mac, Linux, and Windows to see if local AI is production-ready. Sat, 13 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) OpenClaw Review: 345k Stars But Is It Secure? https://aikickstart.com.au/news/openclaw-review-2026 https://aikickstart.com.au/news/openclaw-review-2026 OpenClaw is the most-starred AI agent framework on GitHub. We reviewed its architecture, security model, and whether the hype matches reality. Sun, 14 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Hermes Agent Review: The Learning Agent That Improves Itself https://aikickstart.com.au/news/hermes-agent-review-2026 https://aikickstart.com.au/news/hermes-agent-review-2026 Hermes Agent is a self-improving AI agent that learns from its mistakes. We ran it for 2 weeks on real tasks to see if the learning loop actually works. Sun, 14 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) OpenHuman Review: Desktop-First Personal AI https://aikickstart.com.au/news/openhuman-review-2026 https://aikickstart.com.au/news/openhuman-review-2026 OpenHuman is a desktop-first personal AI with 118+ integrations. We tested its privacy model, plugin system, and the TokenJuice economy over 2 weeks. Sun, 14 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) ComfyUI Review: Node-Based AI Image Generation https://aikickstart.com.au/news/comfyui-review-2026 https://aikickstart.com.au/news/comfyui-review-2026 ComfyUI is the power user's pick for AI image generation, with a node-based workflow. We tested it against Midjourney and Stable Diffusion UIs. Mon, 15 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Runway Gen-4 Review: AI Video Generation at Scale https://aikickstart.com.au/news/runway-gen-4-review-2026 https://aikickstart.com.au/news/runway-gen-4-review-2026 Runway Gen-4 makes professional video from text and images, from $12/mo. We tested its quality, shot consistency, and commercial viability. Mon, 15 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) ElevenLabs Review: Voice Cloning and Text-to-Speech https://aikickstart.com.au/news/elevenlabs-review-2026 https://aikickstart.com.au/news/elevenlabs-review-2026 ElevenLabs produces the most realistic AI voices available. We tested voice cloning, multilingual support, and the new AI sound effects feature. Mon, 15 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Firecrawl Review: Web Context for AI Agents (130k Stars) https://aikickstart.com.au/news/firecrawl-review-2026 https://aikickstart.com.au/news/firecrawl-review-2026 Firecrawl turns any website into clean, LLM-ready data. With 130k+ GitHub stars, we tested its accuracy, speed, and the new context API. Tue, 16 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Dify Review: Build LLM Apps Visually (136k Stars) https://aikickstart.com.au/news/dify-review-2026 https://aikickstart.com.au/news/dify-review-2026 Dify is an open-source platform for building LLM apps without code. With 136k stars, we tested its visual builder, RAG system, and deployment. Tue, 16 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Langflow Review: Visual Agent Builder (146k Stars) https://aikickstart.com.au/news/langflow-review-2026 https://aikickstart.com.au/news/langflow-review-2026 Langflow builds AI agents by dragging and dropping components. With 146k stars, we tested its flexibility, performance, and production readiness. Tue, 16 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Mem0 Review: Agent Memory That Persists (52k Stars) https://aikickstart.com.au/news/mem0-review-2026 https://aikickstart.com.au/news/mem0-review-2026 Mem0 gives AI agents long-term memory. With 52k stars, we tested its persistence, retrieval accuracy, and how hard it is to integrate. Wed, 17 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Browser-use Review: Browser Control for AI Agents https://aikickstart.com.au/news/browser-use-review-2026 https://aikickstart.com.au/news/browser-use-review-2026 Browser-use gives AI agents the ability to control browsers programmatically. We tested it on 25 real-world web tasks to see if it's production-ready. Wed, 17 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) LocalAI Review: Run Models on Any Hardware (44k Stars) https://aikickstart.com.au/news/localai-review-2026 https://aikickstart.com.au/news/localai-review-2026 LocalAI is an OpenAI-compatible API for local models. We tested it on CPU-only, GPU, and edge hardware to see if it truly runs on anything. Wed, 17 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) n8n Review: Workflow Automation Meets AI https://aikickstart.com.au/news/n8n-review-2026 https://aikickstart.com.au/news/n8n-review-2026 n8n adds AI nodes to its workflow automation platform. We tested the new AI features, self-hosted vs cloud options, and whether it competes with Zapier. Thu, 18 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Make Review: No-Code Automation for AI Workflows https://aikickstart.com.au/news/make-review-2026 https://aikickstart.com.au/news/make-review-2026 Make (formerly Integromat) brings visual workflow automation to AI applications. We tested its 2,000+ app integrations and AI module capabilities. Thu, 18 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Pinecone Review: Vector Database for RAG https://aikickstart.com.au/news/pinecone-review-2026 https://aikickstart.com.au/news/pinecone-review-2026 Pinecone is the managed vector database purpose-built for AI. We tested ingestion speed, query latency, and metadata filtering at scale. Thu, 18 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Weaviate Review: Open-Source Vector Search https://aikickstart.com.au/news/weaviate-review-2026 https://aikickstart.com.au/news/weaviate-review-2026 Weaviate is an open-source vector database with native semantic search. We tested self-hosted and managed options, GraphQL interface, and module ecosystem. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Chroma Review: The Embedded Vector Database https://aikickstart.com.au/news/chroma-review-2026 https://aikickstart.com.au/news/chroma-review-2026 A hands-on review of Chroma, the embedded vector database, covering its Python-first API, persistence, and fit against production stores. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) 200ms: Pinecone Serverless or Chroma Cloud Dataset > 500k docs: Weaviate Cloud or Chroma Cloud Multi-user concurrency: Any managed service Need hybrid search at scale: Pinecone, Weaviate, or Chroma Cloud Team needs shared access: Pinecone, Weaviate, or Chroma Cloud Pros and Cons: Easiest setup in category: Local single-node engine isn't built for millions of docs Great for learning: Slower at scale than managed competitors Zero configuration: Fewer features than the heavyweight platforms Strong for prototyping: Local mode is single-process Free and open-source: Cloud scale means moving to the paid hosted tier A note on the cons: an older version of this review listed "no managed cloud option," which is no longer accurate. Chroma Cloud is a live, fully managed serverless service from the Chroma team, with multi-region hosting on AWS and GCP and usage-based billing. Verdict: Score: 8.0/10: Chroma is the "hello world" of vector databases, and that's a compliment. If you're learning RAG, start here, the simplicity is deliberate, and it saves you hours you'd otherwise spend wrestling with infrastructure. The honest caveat is just that the free local version is a starting point. When you need scale, concurrency, or shared team access, you either move to Chroma's own hosted tier or weigh up a managed alternative. Knowing where that line sits for your project is the whole skill. This review was run against an earlier Chroma release; as of mid-2026 the project has moved well past it (current releases are tracked on [GitHub](https://github.com/chroma-core/chroma/releases)), so check the version you're installing before relying on any specific behaviour here. *Published June 19, 2026*]]> Supabase Review: Postgres for AI Applications https://aikickstart.com.au/news/supabase-review-2026 https://aikickstart.com.au/news/supabase-review-2026 Supabase puts vector search, edge functions, and real-time on Postgres. We tested it as an AI app backend and weighed it against Firebase. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) query_embedding LIMIT 5; We ran our own test with 500k vectors. To be upfront: these are our in-house numbers, not a published, peer-reviewed benchmark, so treat them as a directional read rather than gospel. Ingestion: 2m 30s Query latency (p99): 45ms Hybrid search: available with tsvector (see the [Supabase hybrid search docs](https://supabase.com/docs/guides/ai/hybrid-search)) That is slower than a dedicated vector store. Pinecone has quoted a 45ms p99 on its dedicated read nodes, with much lower figures in other configurations, so the gap depends heavily on how each system is set up ([Blocks & Files reporting](https://www.blocksandfiles.com/ai-ml/2026/04/15/pinecone-claims-up-to-97-lower-costs-with-dedicated-read-nodes/5217712)). For most AI apps, 45ms is well within the range users won't notice. The payoff is keeping your relational data and your vectors in the same query, which spares you a second database to run and sync. AI App Architecture: A typical AI app on Supabase looks like this: **Documents table**, with a vector column **Users table**, with RLS policies **Edge Functions**, for LLM calls and webhooks **Real-time**, live UI updates **Auth**, secure user management One platform, one database, and no external services for most builds. That is the whole argument for the platform in a single sentence. Pros and Cons: Postgres + vectors in one: Vector search slower than dedicated Generous free tier: Team tier is expensive Real-time subscriptions: Edge Functions cold start (~200ms reported) Excellent auth system: Self-hosted needs expertise Great documentation: Connection pooling limits On the cold-start figure: Supabase's own [Edge Functions architecture docs](https://supabase.com/docs/guides/functions/architecture) cite much lower numbers, often in the 0-5ms range on the [Deno runtime](https://supabase.com/features/deno-edge-functions). The ~200ms we list is plausible for heavier functions but is not the typical documented figure, so don't plan capacity around it without testing your own functions first. Verdict: Score: 9.0/10: Supabase is our default recommendation for AI application backends. Putting relational data, vector search, auth, and real-time behind one database cuts out most of the integration work that usually eats a team's first month. Start on the free tier, prove out your app, and scale when the usage is real. The score is our editorial call, not a measured fact, but it reflects how rarely we hit a reason to reach for something else. *Published June 19, 2026 | Supabase tested with [pgvector v0.8](https://www.postgresql.org/about/news/pgvector-080-released-2952)*]]> LangGraph Review: Agent Orchestration from LangChain https://aikickstart.com.au/news/langgraph-review-2026 https://aikickstart.com.au/news/langgraph-review-2026 LangGraph models agents as graphs with loops, checkpoints, and approval gates. We tested its persistence and human-in-the-loop in production. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) CrewAI Review: Multi-Agent Collaboration Framework https://aikickstart.com.au/news/crewai-review-2026 https://aikickstart.com.au/news/crewai-review-2026 CrewAI lets you build teams of AI agents that work together. We tested its role-based architecture, collaboration patterns, and compared it to AutoGen. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) AutoGen Review: Microsoft's Multi-Agent Framework https://aikickstart.com.au/news/autogen-review-2026 https://aikickstart.com.au/news/autogen-review-2026 AutoGen from Microsoft Research builds conversational agent systems. We tested its group chat, code execution, and nested chat for enterprise work. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Aider Review: Terminal AI Coding Assistant https://aikickstart.com.au/news/aider-review-2026 https://aikickstart.com.au/news/aider-review-2026 Aider brings AI coding to the terminal, with git built in and any LLM behind it. We put it up against Cursor and Copilot across real edits. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Continue.dev Review: Open-Source Coding Assistant https://aikickstart.com.au/news/continue-dev-review-2026 https://aikickstart.com.au/news/continue-dev-review-2026 Continue.dev is a free, open-source AI coding assistant for any IDE. We tested its autocomplete, chat, and edit tools against Copilot and Cursor. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Tabnine Review: AI Code Completion for Enterprises https://aikickstart.com.au/news/tabnine-review-2026 https://aikickstart.com.au/news/tabnine-review-2026 Tabnine sells enterprise AI code completion with real privacy guarantees. We tested its self-hosted option, team model training, and suggestions. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Amazon CodeWhisperer Review: AWS's Coding Assistant https://aikickstart.com.au/news/amazon-codewhisperer-review-2026 https://aikickstart.com.au/news/amazon-codewhisperer-review-2026 CodeWhisperer is AWS's AI coding assistant with deep service integration. We tested its code generation, security scanning, and AWS-specific features. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) JetBrains AI Review: IDE-Native AI Assistance https://aikickstart.com.au/news/jetbrains-ai-review-2026 https://aikickstart.com.au/news/jetbrains-ai-review-2026 JetBrains builds AI straight into IntelliJ, PyCharm, and its other IDEs. We tested AI Assistant, local models, and how it stacks up against Copilot. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Vercel v0 Review: AI-Generated UI Components https://aikickstart.com.au/news/vercel-v0-review-2026 https://aikickstart.com.au/news/vercel-v0-review-2026 v0 generates React components from text descriptions and images. We tested its design accuracy, code quality, and integration with existing projects. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Bolt.new Review: Full-Stack AI Deployment https://aikickstart.com.au/news/bolt-new-review-2026 https://aikickstart.com.au/news/bolt-new-review-2026 Bolt.new builds and ships a full-stack app from one prompt. We tested its React and Node.js output, database wiring, and how reliably it deploys. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Tempo Review: AI-Generated React Applications https://aikickstart.com.au/news/tempo-review-2026 https://aikickstart.com.au/news/tempo-review-2026 Tempo builds full React apps from prompts and bets on design quality. We tested its components, design-system fit, and the day-to-day workflow. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Lovable Review: AI Full-Stack Engineer https://aikickstart.com.au/news/lovable-review-2026 https://aikickstart.com.au/news/lovable-review-2026 Lovable claims to be a full-stack AI engineer in a box. We tested its ability to build, deploy, and maintain complete web applications. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Pi Coding Agent Review: The Real Claude Code Competitor https://aikickstart.com.au/news/pi-coding-agent-review-2026 https://aikickstart.com.au/news/pi-coding-agent-review-2026 Pi Coding Agent from Inflection AI takes a conversational tack on coding. We tested it against Claude Code and Cursor to see if it holds up. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Google Agents CLI Review: AI Agents from the Terminal https://aikickstart.com.au/news/google-agents-cli-review-2026 https://aikickstart.com.au/news/google-agents-cli-review-2026 Google Agents CLI is the newest entrant in the agent development space. We tested its deployment pipeline, GCP integration, and developer experience. Fri, 19 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Claude Fable 5 review: most capable, then banned https://aikickstart.com.au/news/claude-fable-5-review-anthropic-most-capable-model-banned https://aikickstart.com.au/news/claude-fable-5-review-anthropic-most-capable-model-banned Anthropic's Claude Fable 5 launched 9 June 2026 with a field-leading 80.3% on SWE-bench Pro. Three days later it was suspended. We review what happened. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Claude Opus 4.8 review: The current Anthropic workhorse https://aikickstart.com.au/news/claude-opus-4-8-review-anthropic-workhorse https://aikickstart.com.au/news/claude-opus-4-8-review-anthropic-workhorse Claude Opus 4.8 lands at 69.2% SWE-bench Pro and 89.8% MMLU with a 1M beta context. At $5/$25 per million tokens, it is Anthropic's current best. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Claude Opus 4.7 review: Is the upgrade to 4.8 worth it? https://aikickstart.com.au/news/claude-opus-4-7-vs-4-8-worth-upgrading https://aikickstart.com.au/news/claude-opus-4-7-vs-4-8-worth-upgrading Claude Opus 4.7 scores 63.8% on SWE-bench Pro and 89.2% on MMLU with a 1M beta context. It costs the same as 4.8, so is there any reason to stay? Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Claude Sonnet 4.6 review: near-Opus, far cheaper https://aikickstart.com.au/news/claude-sonnet-4-6-opus-intelligence-half-price https://aikickstart.com.au/news/claude-sonnet-4-6-opus-intelligence-half-price Claude Sonnet 4.6 hits 58.1% SWE-bench Pro and 87.6% MMLU for $3/$15 per million tokens, 40% under Opus 4.8. We test whether the trade-off pays. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) GPT-5.5 review: OpenAI's 'Spud' codename explained https://aikickstart.com.au/news/gpt-5-5-review-openai-spud-codename https://aikickstart.com.au/news/gpt-5-5-review-openai-spud-codename GPT-5.5 launched 23 April 2026 at 58.6% SWE-bench Pro and 88.4% MMLU with a 400K context. The 'Spud' codename hinted at a small but capable model. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) GPT-5.5 Pro review: Is the $8/$40 upgrade worth it? https://aikickstart.com.au/news/gpt-5-5-pro-review-80-dollar-upgrade-worth-it https://aikickstart.com.au/news/gpt-5-5-pro-review-80-dollar-upgrade-worth-it GPT-5.5 Pro costs $8/$40 per million tokens and scores 62.4% SWE-bench Pro and 89.7% MMLU. Does the 60% jump over base GPT-5.5 actually pay off? Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) GPT-5.5 Instant review: The default ChatGPT model tested https://aikickstart.com.au/news/gpt-5-5-instant-review-default-chatgpt-model https://aikickstart.com.au/news/gpt-5-5-instant-review-default-chatgpt-model GPT-5.5 Instant powers default ChatGPT. At $0.50/$1.50 and 128K context, it scores 42.1% SWE-bench Pro and 84.2% MMLU. Is that good enough? Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Gemini 3.5 Flash review: frontier scores, low price https://aikickstart.com.au/news/gemini-3-5-flash-frontier-performance-flash-pricing https://aikickstart.com.au/news/gemini-3-5-flash-frontier-performance-flash-pricing Gemini 3.5 Flash launched 19 May 2026 at 48.2% SWE-bench Pro and 86.8% MMLU with a 1M context, for $0.35/$0.70 per million tokens. We test the value pick. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Gemini 3.1 Pro review: ARC-AGI-2 at 77.1% https://aikickstart.com.au/news/gemini-3-1-pro-arc-agi-2-77-1 https://aikickstart.com.au/news/gemini-3-1-pro-arc-agi-2-77-1 Gemini 3.1 Pro launched 19 February 2026 with 54.2% SWE-bench Pro, 88.1% MMLU, and a standout 77.1% on ARC-AGI-2. We review Google's reasoning specialist. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) MiniMax M3 review: Open-weights with 1M context, tested https://aikickstart.com.au/news/minimax-m3-open-weights-1m-context-tested https://aikickstart.com.au/news/minimax-m3-open-weights-1m-context-tested MiniMax M3 launched 1 June 2026 at 59.0% SWE-bench Pro and 86.4% MMLU with a 1M context. At $0.30/$1.20 per million tokens, it is the open-weights pick. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) GLM-5.2 review: 753B-parameter open-weights model https://aikickstart.com.au/news/glm-5-2-review-753b-parameters-open-weights-chinese https://aikickstart.com.au/news/glm-5-2-review-753b-parameters-open-weights-chinese Zhipu AI's GLM-5.2 hits 51.4% SWE-bench Pro and 85.2% MMLU with 256K context. At $0.80/$2.40 per million tokens, it is China's top open-weights model. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Kimi K2.7-Code review: Moonshot's coding specialist https://aikickstart.com.au/news/kimi-k2-7-code-review-moonshot-coding-specialist https://aikickstart.com.au/news/kimi-k2-7-code-review-moonshot-coding-specialist Moonshot's Kimi K2.7-Code scores 56.8% SWE-bench Pro and 85.7% MMLU with 256K context. At $0.50/$2.00 per million tokens, it is built for software work. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) DeepSeek V3.5 review: $0.15 per million input tokens https://aikickstart.com.au/news/deepseek-v3-5-review-15-cent-per-million-input https://aikickstart.com.au/news/deepseek-v3-5-review-15-cent-per-million-input DeepSeek V3.5 reportedly hits 52.4% SWE-bench Pro and 85.8% MMLU with a 1M context. At $0.15/$0.60, it is the cheapest million-token model. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Llama 4 review: Meta's MoE open model https://aikickstart.com.au/news/llama-4-review-meta-moe-open-model https://aikickstart.com.au/news/llama-4-review-meta-moe-open-model Meta's Llama 4 is a free open-weights MoE model with strong MMLU and a large context. Free to download, but running it still costs GPUs or a paid API. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Grok 4 review: xAI's real-time data advantage https://aikickstart.com.au/news/grok-4-review-xai-real-time-data-advantage https://aikickstart.com.au/news/grok-4-review-xai-real-time-data-advantage xAI's Grok 4 posts 54.8% SWE-bench Pro and 87.2% MMLU with a 256K context. At $5/$25 per million tokens, its real draw is live X data access. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Qwen 3 review: Alibaba's coding-capable open model https://aikickstart.com.au/news/qwen-3-review-alibaba-coding-open-model https://aikickstart.com.au/news/qwen-3-review-alibaba-coding-open-model Alibaba's Qwen 3 posts 46.2% SWE-bench Pro and 84.6% MMLU with a 128K context. At $0.40/$1.20 per million, it's a solid multilingual open-weights pick. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Mistral Large 2 review: European multilingual champion https://aikickstart.com.au/news/mistral-large-2-review-european-multilingual-champion https://aikickstart.com.au/news/mistral-large-2-review-european-multilingual-champion Mistral Large 2 posts 48.6% SWE-bench Pro and 85.1% MMLU with a 256K context. At $2/$6 per million tokens, it's the strongest European-built model around. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Claude Fable 5 vs GPT-5.5: What the benchmarks say https://aikickstart.com.au/news/claude-fable-5-vs-gpt-5-5-benchmarks https://aikickstart.com.au/news/claude-fable-5-vs-gpt-5-5-benchmarks Anthropic's suspended Claude Fable 5 (80.3% SWE-bench Pro, 92.1% MMLU) vs OpenAI's GPT-5.5 (58.6% SWE-bench Pro, 88.4% MMLU). The numbers are stark. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Claude Opus 4.8 vs Gemini 3.1 Pro: Head-to-head https://aikickstart.com.au/news/claude-opus-4-8-vs-gemini-3-1-pro-head-to-head https://aikickstart.com.au/news/claude-opus-4-8-vs-gemini-3-1-pro-head-to-head Anthropic's Opus 4.8 ($5/$25, 69.2% SWE-bench Pro) vs Google's Gemini 3.1 Pro ($3.50/$10.50, 54.2%). Two premium models, very different strengths. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) MiniMax M3 vs DeepSeek V3.5: Best open-weights model? https://aikickstart.com.au/news/minimax-m3-vs-deepseek-v3-5-best-open-weights https://aikickstart.com.au/news/minimax-m3-vs-deepseek-v3-5-best-open-weights MiniMax M3 ($0.30/$1.20, 59.0% SWE-bench Pro) vs DeepSeek V3.5 ($0.15/$0.60, 52.4%). Both run a 1M context on open licences. Which one should you pick? Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) GLM-5.2 vs Kimi K2.7-Code: Chinese models compared https://aikickstart.com.au/news/glm-5-2-vs-kimi-k2-7-code-chinese-models-compared https://aikickstart.com.au/news/glm-5-2-vs-kimi-k2-7-code-chinese-models-compared Zhipu AI's GLM-5.2 ($0.80/$2.40, 51.4% SWE-bench Pro) vs Moonshot's Kimi K2.7-Code ($0.50/$2.00, 56.8%). Two top Chinese open-weights models, compared. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) GPT-5.5 vs Claude Sonnet 4.6: Best $5-tier model https://aikickstart.com.au/news/gpt-5-5-vs-claude-sonnet-4-6-best-5-dollar-tier https://aikickstart.com.au/news/gpt-5-5-vs-claude-sonnet-4-6-best-5-dollar-tier OpenAI's GPT-5.5 ($5/$30, 58.6% SWE-bench Pro) vs Anthropic's Sonnet 4.6 ($3/$15, 58.1%). Near-identical coding scores, very different prices. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Gemini 3.5 Flash vs GPT-5.5 Instant: Best budget model https://aikickstart.com.au/news/gemini-3-5-flash-vs-gpt-5-5-instant-best-budget https://aikickstart.com.au/news/gemini-3-5-flash-vs-gpt-5-5-instant-best-budget Google's Gemini 3.5 Flash ($0.35/$0.70, 86.8% MMLU, 1M context) vs OpenAI's GPT-5.5 Instant ($0.50/$1.50, 84.2% MMLU, 128K). The budget-tier face-off. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Llama 4 vs Qwen 3 vs Mistral Large 2: Open model showdown https://aikickstart.com.au/news/llama-4-vs-qwen-3-vs-mistral-large-2-open-showdown https://aikickstart.com.au/news/llama-4-vs-qwen-3-vs-mistral-large-2-open-showdown Three open-weights models compared: Meta's Llama 4 (free), Alibaba's Qwen 3 ($0.40/$1.20), and Mistral Large 2 ($2/$6). Which one fits your stack? Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) The $1-per-million club: Cheapest capable models https://aikickstart.com.au/news/one-dollar-per-million-club-cheapest-capable-models https://aikickstart.com.au/news/one-dollar-per-million-club-cheapest-capable-models Which models do real work under $1 per million input tokens? We rank DeepSeek V3.5 ($0.15), Gemini Flash ($0.35), Qwen 3 ($0.40), and GPT-5.5 Instant. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Coding benchmarks: Which model writes the best code? https://aikickstart.com.au/news/coding-benchmarks-which-model-writes-best-code https://aikickstart.com.au/news/coding-benchmarks-which-model-writes-best-code We rank 17 models by SWE-bench Pro. Claude Fable 5 leads at 80.3%, then Opus 4.8 at 69.2% and GPT-5.5 Pro at 62.4%. The full coding leaderboard. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) 1M context models tested: MiniMax M3 vs Gemini 3.5 Flash https://aikickstart.com.au/news/1m-context-models-tested-minimax-m3-vs-gemini-3-5-flash https://aikickstart.com.au/news/1m-context-models-tested-minimax-m3-vs-gemini-3-5-flash MiniMax M3 ($0.30/$1.20, 59.0% SWE-bench Pro) and Gemini 3.5 Flash ($0.35/$0.70, 48.2%) both run 1M-token contexts. We test which handles long docs better. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) The suspended model: What we learned from Claude Fable 5 https://aikickstart.com.au/news/suspended-model-what-we-learned-claude-fable-5 https://aikickstart.com.au/news/suspended-model-what-we-learned-claude-fable-5 What Claude Fable 5, suspended three days after launch by a US export-control order, teaches us about AI capability, safety, and policy. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Agentic coding: Best models for multi-agent systems https://aikickstart.com.au/news/agentic-coding-best-models-multi-agent-systems https://aikickstart.com.au/news/agentic-coding-best-models-multi-agent-systems Multi-agent coding needs strong SWE-bench Pro scores, big contexts, and reliable tool use. We rank Opus 4.8, MiniMax M3, GPT-5.5 Pro, and Sonnet 4.6. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Chinese AI models: GLM-5.2, Kimi K2.7, Qwen 3, DeepSeek https://aikickstart.com.au/news/chinese-ai-models-glm-kimi-qwen-deepseek https://aikickstart.com.au/news/chinese-ai-models-glm-kimi-qwen-deepseek A review of four leading Chinese open-weights models, GLM-5.2, Kimi K2.7, Qwen 3, and DeepSeek, and their price-to-capability edge. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) European AI: Mistral's strategy vs American giants https://aikickstart.com.au/news/european-ai-mistral-strategy-vs-american-giants https://aikickstart.com.au/news/european-ai-mistral-strategy-vs-american-giants Mistral Large 2 ($2/$6, 48.6% SWE-bench Pro) is Europe's best answer to US closed models. How its open-weights strategy stacks up against the US labs. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Model pricing wars: June 2026 comparison table https://aikickstart.com.au/news/model-pricing-wars-june-2026-comparison-table https://aikickstart.com.au/news/model-pricing-wars-june-2026-comparison-table A full price comparison of 17 models. Input runs from free (Llama 4) to $10/1M (Claude Fable 5); output from free to $50/1M. The whole pricing picture. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Best free models: Llama 4, Qwen 3, and self-hosted options https://aikickstart.com.au/news/best-free-models-llama-4-qwen-self-hosted https://aikickstart.com.au/news/best-free-models-llama-4-qwen-self-hosted Llama 4's weights are free; Qwen 3 is $0.40/$1.20 by API but free to download. The best zero-cost AI options and the hardware you need to run them. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Best model for RAG systems: Context vs accuracy https://aikickstart.com.au/news/best-model-rag-systems-context-vs-accuracy https://aikickstart.com.au/news/best-model-rag-systems-context-vs-accuracy RAG needs a big context for retrieved text and high MMLU for comprehension. We rank Gemini Flash, DeepSeek V3.5, MiniMax M3, and Opus 4.8 for retrieval. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Best model for coding: SWE-bench Pro leaderboard https://aikickstart.com.au/news/best-model-coding-swe-bench-pro-leaderboard https://aikickstart.com.au/news/best-model-coding-swe-bench-pro-leaderboard The June 2026 SWE-bench Pro coding leaderboard, with Claude Fable 5 in the lead and a full tier-by-tier breakdown for engineering teams. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Best model for startups: Cost-effective AI in 2026 https://aikickstart.com.au/news/best-model-startups-cost-effective-ai-2026 https://aikickstart.com.au/news/best-model-startups-cost-effective-ai-2026 The most cost-effective AI models for startups in 2026, comparing DeepSeek, Gemini Flash, and MiniMax on price and real capability. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) The open-weights advantage: Why open models are winning https://aikickstart.com.au/news/open-weights-advantage-why-open-models-winning https://aikickstart.com.au/news/open-weights-advantage-why-open-models-winning MiniMax M3 (59.0% SWE-bench), DeepSeek V3.5 (52.4%), and Llama 4 (free) show open-weights models can compete with closed ones. Why openness is winning. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Model deprecation timeline: What's being phased out https://aikickstart.com.au/news/model-deprecation-timeline-whats-being-phased-out https://aikickstart.com.au/news/model-deprecation-timeline-whats-being-phased-out Claude Opus 4.7 is effectively obsolete. GPT-4o is history. We track which models are being phased out in 2026 and what you should migrate to. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) ARC-AGI-2 leaderboard: Which models reason best? https://aikickstart.com.au/news/arc-agi-2-leaderboard-which-models-reason-best https://aikickstart.com.au/news/arc-agi-2-leaderboard-which-models-reason-best ARC-AGI-2 tests fluid intelligence and abstract reasoning. Gemini 3.1 Pro leads at 77.1%; most models land between 60-75%. What the benchmark really shows. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) June 2026 model buying guide: Which AI to use for what https://aikickstart.com.au/news/june-2026-model-buying-guide-ai-for-what https://aikickstart.com.au/news/june-2026-model-buying-guide-ai-for-what How to choose an AI model in June 2026. We map 17 models to 12 jobs, from coding to support to document analysis, with pricing and benchmarks. Mon, 15 Jun 2026 00:00:00 GMT Model Review daniel.fleuren@aikickstart.com.au (Daniel Fleuren) How OpenClaw became GitHub's biggest AI agent repo https://aikickstart.com.au/news/openclaw-345k-stars-biggest-ai-agent-repo https://aikickstart.com.au/news/openclaw-345k-stars-biggest-ai-agent-repo How OpenClaw became one of GitHub's most-starred AI agent repos, what its rise says about agentic AI, and where the hype outruns the evidence. Mon, 15 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Hermes Agent: Nous Research's learning agent explained https://aikickstart.com.au/news/hermes-agent-nous-research-learning-agent https://aikickstart.com.au/news/hermes-agent-nous-research-learning-agent Inside the 22k-star learning agent from Nous Research that uses Honcho memory and 40+ tools to build a dialectic understanding of its users. Sun, 14 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) OpenHuman: Desktop-first personal AI with 118+ integrations https://aikickstart.com.au/news/openhuman-desktop-first-personal-ai https://aikickstart.com.au/news/openhuman-desktop-first-personal-ai OpenHuman brings personal AI to your desktop with Tauri, 118+ integrations, and a unique Memory Tree knowledge system, all under GPLv3. Sat, 13 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) nanochat: Karpathy's minimal LLM training stack https://aikickstart.com.au/news/nanochat-karpathy-minimal-llm-training-stack https://aikickstart.com.au/news/nanochat-karpathy-minimal-llm-training-stack Andrej Karpathy's nanochat trains a GPT-2 class model for about $48. Here is why 55,000 developers have starred this readable, end-to-end training stack. Fri, 12 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Firecrawl: the web context API behind AI agents https://aikickstart.com.au/news/firecrawl-web-context-api-ai-agents https://aikickstart.com.au/news/firecrawl-web-context-api-ai-agents Firecrawl has become the de facto standard for turning websites into LLM-ready data. Here's how it reached 130k+ stars and top 100 GitHub status. Thu, 11 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Bumblebee: Perplexity's supply chain security scanner https://aikickstart.com.au/news/bumblebee-perplexity-supply-chain-scanner https://aikickstart.com.au/news/bumblebee-perplexity-supply-chain-scanner Perplexity open-sourced Bumblebee v0.1.1, a supply chain scanner covering npm, PyPI, MCP servers, VS Code extensions, and browser plugins. Wed, 10 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) awesome-claude-skills: 1000+ skills for Claude Code https://aikickstart.com.au/news/awesome-claude-skills-1000-production-ready https://aikickstart.com.au/news/awesome-claude-skills-1000-production-ready The community-curated skill library that turns Claude Code into a universal development assistant with over 1000 production-ready capabilities. Tue, 09 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Langflow: Building agents without code (146k stars) https://aikickstart.com.au/news/langflow-building-agents-without-code-146k https://aikickstart.com.au/news/langflow-building-agents-without-code-146k Langflow's visual agent builder has hit 146,000 GitHub stars. We look at how drag-and-drop construction is putting agents within reach of non-coders. Mon, 08 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Dify: The LLM app development platform (136k stars) https://aikickstart.com.au/news/dify-llm-app-development-platform-136k https://aikickstart.com.au/news/dify-llm-app-development-platform-136k Dify combines visual workflow design, RAG pipelines, and model management into a complete platform for building LLM applications at scale. Sun, 07 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Mem0: Giving agents persistent memory (52k stars) https://aikickstart.com.au/news/mem0-giving-agents-persistent-memory-52k https://aikickstart.com.au/news/mem0-giving-agents-persistent-memory-52k Mem0 fixes the amnesia problem in AI agents with a memory layer that persists across sessions. 52,000 developers have already starred the project. Sat, 06 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Browser-use: Let agents browse the web (86k stars) https://aikickstart.com.au/news/browser-use-agents-browse-the-web-86k https://aikickstart.com.au/news/browser-use-agents-browse-the-web-86k Browser-use gives AI agents the ability to navigate websites, fill forms, and extract data, all through a natural language interface with 86,000 stars. Fri, 05 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) LocalAI: Run any model on any hardware (44k stars) https://aikickstart.com.au/news/localai-run-any-model-any-hardware-44k https://aikickstart.com.au/news/localai-run-any-model-any-hardware-44k LocalAI lets you run LLMs, diffusion models, and embeddings locally without a GPU. Here's how 44,000 developers are self-hosting AI. Thu, 04 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) MetaGPT: Multi-agent teams that build software https://aikickstart.com.au/news/metagpt-multi-agent-teams-build-software https://aikickstart.com.au/news/metagpt-multi-agent-teams-build-software MetaGPT simulates an entire software company with specialised AI agents that collaborate to design, code, test, and deploy applications. Wed, 03 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) CrewAI: Collaborative AI agents framework https://aikickstart.com.au/news/crewai-collaborative-ai-agents-framework https://aikickstart.com.au/news/crewai-collaborative-ai-agents-framework CrewAI makes multi-agent collaboration simple with role-based agents, task delegation, and process flows. Here's how it works. Tue, 02 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) AutoGen: Microsoft's agent orchestration toolkit https://aikickstart.com.au/news/autogen-microsoft-agent-orchestration-toolkit https://aikickstart.com.au/news/autogen-microsoft-agent-orchestration-toolkit Microsoft's AutoGen framework enables complex multi-agent conversations with human participation, code execution, and flexible agent patterns. Mon, 01 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) The OpenClaw security audit: CVE-2026-25253 explained https://aikickstart.com.au/news/openclaw-security-audit-cve-2026-25253 https://aikickstart.com.au/news/openclaw-security-audit-cve-2026-25253 CVE-2026-25253 was a one-click remote code execution bug in OpenClaw, caused by token theft, not prompt injection. Here is what broke and why it matters. Wed, 10 Jun 2026 00:00:00 GMT AI News daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Hermes vs OpenClaw: Architecture comparison https://aikickstart.com.au/news/hermes-vs-openclaw-architecture-comparison https://aikickstart.com.au/news/hermes-vs-openclaw-architecture-comparison Two of the most popular open-source AI agents take fundamentally different approaches. We compare their architectures, philosophies, and use cases. Tue, 09 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) OpenClaw's ClawHub: The skill marketplace ecosystem https://aikickstart.com.au/news/openclaw-clawhub-skill-marketplace-ecosystem https://aikickstart.com.au/news/openclaw-clawhub-skill-marketplace-ecosystem How ClawHub became the npm of AI agent skills, with thousands of community-contributed capabilities and a thriving developer economy. Mon, 08 Jun 2026 00:00:00 GMT AI News daniel.fleuren@aikickstart.com.au (Daniel Fleuren) ` (for example, `clawhub install @openclaw/demo`). Worth knowing before you copy and paste. In the npm-style model the original article describes, each skill package was said to include: **Manifest**: Metadata describing capabilities, requirements, and permissions **Implementation**: TypeScript code implementing the skill's logic **Schema**: Input/output definitions for the LLM to understand usage **Documentation**: Usage examples, configuration options, and testing guides **Tests**: Automated tests verifying skill behaviour In practice, [OpenClaw's own docs](https://docs.openclaw.ai/clawhub) point to something leaner: a real skill is mostly a `SKILL.md` holding instructions and frontmatter metadata, with optional scripts or config alongside. Some bundled plugins do carry code, but the TypeScript-package breakdown above is not how most text-based skills are actually put together. The Skill Economy: ClawHub has grown its own little economy. Skill authors build a reputation through downloads, ratings, and word of mouth. Some have reportedly turned that visibility into consulting work, writing custom skills for businesses that want something off-menu. The original article listed these as the most downloaded skills: **@clawhub/research-agent** (2M+ downloads): Multi-step web research with synthesis **@clawhub/code-reviewer** (1.5M+ downloads): Automated code review with best practices **@clawhub/data-analyst** (1.2M+ downloads): SQL generation, visualisation, and insight extraction **@clawhub/devops** (900K+ downloads): CI/CD pipeline management and deployment **@clawhub/content-writer** (800K+ downloads): Blog posts, documentation, and marketing copy Treat that list with caution. These names and figures could not be matched against any real ClawHub leaderboard. Public rankings tell a different story: a [category-by-category guide on Medium](https://medium.com/@tentenco/the-best-clawhub-skills-worth-installing-now-a-category-by-category-guide-5221c4850d21) reports the actual top skills by installs as Skill Vetter (~256K), Github (~189K), Ontology (~188K), Gog (~185K), and Felo Search (~145K). No skill called `@clawhub/research-agent` with two million downloads shows up anywhere we could verify, so the numbers above appear to be invented. Quality and Trust: ClawHub runs a layered approach to keeping skills safe. **Automated Scanning**: Uploaded skills are scanned for malware, secrets, and known vulnerabilities. This part is real, [reporting from Penligent](https://www.penligent.ai/hackinglabs/openclaw-virustotal-clawhub-skill-scanning-turns-the-marketplace-into-a-supply-chain-boundary/) describes VirusTotal scanning and static analysis on submissions. The context matters, though. A lot of that hardening came in response to a supply-chain scare, with more than 1,184 malicious skills reported, so this is less a smoothly engineered system and more a defence that got built in a hurry after things went wrong. **Community Ratings**: Users rate skills on reliability, documentation, and usefulness, and poorly rated ones get flagged for review. **Verified Publishers**: Trusted authors can earn verified status. Cryptographic publisher attestation, stars, and download counts are confirmed features, per the [AllClaw registry overview](https://allclaw.org/entry/clawhub). **Sandbox Testing**: The original article said skills run in a sandbox during installation to check they don't do anything unexpected. Sandboxed execution and behavioural monitoring do come up in security write-ups, but a sandbox step running automatically on every install is not clearly an official, universal ClawHub feature, so take that one as reported rather than confirmed. **Audit Trail**: Semantic versioning with changelogs and easy rollback is real, which makes it straightforward to spot a bad update and revert to a known-good version. Enterprise Features: For organisations, the original article described private registries with the following: **Internal Skills**: Publish proprietary skills without exposing them publicly **Approval Workflows**: Require review before skills can be installed **Usage Analytics**: Track which skills are used across teams **Compliance Scanning**: Automatic licence and security compliance checking **Integration**: Sync with private npm registries and Artifactory A caveat before you plan around any of this: none of these enterprise features could be confirmed against official sources. The [openclaw/clawhub repository](https://github.com/openclaw/clawhub) and the docs we reviewed don't mention private registries, approval workflows, Artifactory sync, or compliance scanning. Security analysts tend to suggest that companies build their own internal trust chain, which hints that these aren't turnkey ClawHub products. If your team needs that kind of control today, assume you may have to build it yourself. The Steinberger Effect: When OpenClaw's founder joined OpenAI in February 2026, people worried about what would happen to ClawHub. Would the marketplace get commercialised? Would the enterprise features end up behind a paywall? One correction first. The original article named "Cole Steinberger." That's wrong. [TechCrunch reported on 15 February 2026](https://techcrunch.com/2026/02/15/openclaw-creator-peter-steinberger-joins-openai/) that it was **Peter** Steinberger, the founder of PSPDFKit, based in Vienna, who joined OpenAI. The handover went better than people feared. [Steinberger's own account](https://steipete.me/posts/2026/openclaw) confirms OpenClaw was committed to staying open-source, living in a foundation that OpenAI would keep supporting. The original article also described a formalised steering committee with named community representatives running ClawHub governance; that specific structure could not be confirmed, so treat it as unverified. The broad point still holds: a well-run open-source project can survive losing its founder. Building a Skill: The original article gave this as a sample skill: import { defineSkill } from '@openclaw/core'; export default defineSkill({ name: 'hello-world', description: 'A simple greeting skill', schema: { input: { name: { type: 'string', description: 'Name to greet' } }, output: { type: 'string' } }, async execute({ name }) { return `Hello, ${name}!`; } }); One thing to flag: this code is illustrative, not verified. No source we checked confirms a `@openclaw/core` package that exports a `defineSkill` helper. As [OpenClaw's skills docs](https://docs.openclaw.ai/tools/skills) describe, real text-based skills are authored as `SKILL.md` folders rather than through a TypeScript `defineSkill()` call. So the sample reads well, but don't expect it to run as-is. The underlying point is sound either way. A skill can be as small as a single function or as involved as a multi-step workflow with API calls, file operations, and branching logic. The Future: According to the original article, ClawHub's roadmap covers skill versioning with dependency management, skill composition (skills that call other skills), and a visual builder for people who don't code. There was also talk of a rating-prediction model to help surface good skills before they've built up downloads. These are forward-looking plans, not shipped features. Semantic versioning already exists, but dependency management, composition, the visual builder, and the prediction model are unconfirmed roadmap items rather than things you can use today. OpenClaw has reached roughly [345,000 GitHub stars](https://en.wikipedia.org/wiki/OpenClaw), and ClawHub is a big part of why. The framework on its own is useful. The registry around it is what makes it a platform, and that gap is worth paying attention to if you're weighing it up for your own team.]]> The Nous Research ecosystem: Hermes, Atropos, DisTrO https://aikickstart.com.au/news/nous-research-ecosystem-hermes-atropos-distro https://aikickstart.com.au/news/nous-research-ecosystem-hermes-atropos-distro Nous Research isn't just building one tool, they're creating a complete ecosystem for AI development. Here's the full picture. Sun, 07 Jun 2026 00:00:00 GMT AI News daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Top 10 GitHub repos every AI developer should star https://aikickstart.com.au/news/top-10-github-repos-ai-developer-should-star https://aikickstart.com.au/news/top-10-github-repos-ai-developer-should-star Our curated list of the most essential open-source repositories for AI developers, from agent frameworks to training stacks to deployment tools. Sat, 06 Jun 2026 00:00:00 GMT AI News daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Open source AI agents: The complete landscape https://aikickstart.com.au/news/open-source-ai-agents-complete-landscape https://aikickstart.com.au/news/open-source-ai-agents-complete-landscape A working map of the open-source AI agent ecosystem in 2026: the frameworks, tools, deployment platforms, and memory systems, and how they fit together. Fri, 05 Jun 2026 00:00:00 GMT AI News daniel.fleuren@aikickstart.com.au (Daniel Fleuren) The business of open source AI: Who's making money? https://aikickstart.com.au/news/business-of-open-source-ai-whos-making-money https://aikickstart.com.au/news/business-of-open-source-ai-whos-making-money A look at the business models behind funded open-source AI projects, and which ones are actually turning real revenue and profit. Thu, 04 Jun 2026 00:00:00 GMT AI News daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Contributing to OpenClaw: A beginner's guide https://aikickstart.com.au/news/contributing-to-openclaw-beginners-guide https://aikickstart.com.au/news/contributing-to-openclaw-beginners-guide Want to contribute to the biggest AI agent repo on GitHub? Here's how to get started, from first issue to first pull request. Wed, 03 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Self-hosting Hermes Agent: Production deployment guide https://aikickstart.com.au/news/self-hosting-hermes-agent-production-deployment https://aikickstart.com.au/news/self-hosting-hermes-agent-production-deployment A step-by-step guide to deploying Hermes Agent in production, from hardware requirements to Honcho memory configuration to monitoring. Tue, 02 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) 2 seconds Error rate > 1% Memory store connection failures LLM API quota exhaustion Scaling: As traffic grows, work through these in order: **Scale the API servers** behind a load balancer **Scale Honcho memory** with read replicas **Cache aggressively** with Redis **Use local models** for high-volume, low-complexity tasks **Implement rate limiting** per user Troubleshooting: A few problems you'll likely hit, and where to start: **High latency**: Check Honcho query performance, switch on Redis caching, and look at whether a faster model would help. **Memory errors**: Grow the PostgreSQL connection pool, add RAM, or bring in read replicas. **LLM rate limits**: Queue requests, add a fallback provider, or shift load to local models. **Tool failures**: Recheck tool permissions, confirm API keys, and make sure the network path is open. Configured properly, Hermes Agent holds up in production and gives you a personalised assistant that gets sharper as it learns your users. The project's popularity says people are paying attention, as of mid-2026 the repository reportedly sits in the high-100-thousands of stars, well above older figures still floating around ([star history](https://www.star-history.com/nousresearch/hermes-agent/)). Just don't read a star count as proof it'll survive your production load. That part is on your deployment.]]> OpenHuman's Memory Trees: How the knowledge system works https://aikickstart.com.au/news/openhuman-memory-trees-knowledge-system https://aikickstart.com.au/news/openhuman-memory-trees-knowledge-system How OpenHuman's Memory Trees work: a hierarchical knowledge system that refreshes every 20 minutes and keeps your files, emails, and notes linked. Mon, 01 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) nanochat: From $48 GPT-2 to understanding LLMs https://aikickstart.com.au/news/nanochat-from-48-dollar-gpt2-understanding-llms https://aikickstart.com.au/news/nanochat-from-48-dollar-gpt2-understanding-llms How Andrej Karpathy's nanochat takes you from complete beginner to understanding every component of a large language model. Sat, 30 May 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Firecrawl MCP server: Agent-native web browsing https://aikickstart.com.au/news/firecrawl-mcp-server-agent-native-web-browsing https://aikickstart.com.au/news/firecrawl-mcp-server-agent-native-web-browsing How Firecrawl's MCP integration is becoming the standard way for AI agents to access web content, with 130k+ stars backing the approach. Fri, 29 May 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) The Mem0 architecture: How agent memory works https://aikickstart.com.au/news/mem0-architecture-how-agent-memory-works https://aikickstart.com.au/news/mem0-architecture-how-agent-memory-works How Mem0's layered memory system gives AI agents persistent, contextual recall across sessions, and which parts of the architecture actually check out. Thu, 28 May 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Browser-use vs Vercel agent-browser https://aikickstart.com.au/news/browser-use-vs-vercel-agent-browser-compared https://aikickstart.com.au/news/browser-use-vs-vercel-agent-browser-compared Two ways to give AI agents a real browser. We compare Browser-use and Vercel's agent-browser on features, architecture and the jobs each one suits best. Wed, 27 May 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) LocalAI vs Ollama: Local model runners compared https://aikickstart.com.au/news/localai-vs-ollama-local-model-runners-compared https://aikickstart.com.au/news/localai-vs-ollama-local-model-runners-compared The two leading tools for running AI models locally take different approaches. We compare features, performance, and ideal use cases. Tue, 26 May 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) The Langflow ecosystem: Visual agent building at scale https://aikickstart.com.au/news/langflow-ecosystem-visual-agent-building-scale https://aikickstart.com.au/news/langflow-ecosystem-visual-agent-building-scale How Langflow's 146k stars power an ecosystem of visual agent development that's transforming how teams build AI applications. Mon, 25 May 2026 00:00:00 GMT AI News daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Dify's RAG pipeline: From documents to answers https://aikickstart.com.au/news/dify-rag-pipeline-documents-to-answers https://aikickstart.com.au/news/dify-rag-pipeline-documents-to-answers Inside Dify's document processing pipeline, which turns unstructured content into accurate, cited answers your team can actually trust. Sun, 24 May 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) CrewAI vs AutoGen vs MetaGPT compared https://aikickstart.com.au/news/crewai-vs-autogen-vs-metagpt-multi-agent-compared https://aikickstart.com.au/news/crewai-vs-autogen-vs-metagpt-multi-agent-compared The three leading multi-agent frameworks take different approaches to agent collaboration. We compare their models, APIs, and ideal use cases. Sat, 23 May 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Open source AI safety: The community's approach https://aikickstart.com.au/news/open-source-ai-safety-community-approach https://aikickstart.com.au/news/open-source-ai-safety-community-approach How the open-source AI community is tackling safety concerns through audits, responsible disclosure, and collaborative standards. Fri, 22 May 2026 00:00:00 GMT AI News daniel.fleuren@aikickstart.com.au (Daniel Fleuren) The OpenClaw fork landscape: After Steinberger joined OpenAI https://aikickstart.com.au/news/openclaw-fork-landscape-after-steinberger-openai https://aikickstart.com.au/news/openclaw-fork-landscape-after-steinberger-openai Cole Steinberger's move to OpenAI in February 2026 catalysed a fork ecosystem. Here's how the post-Steinberger landscape has evolved. Thu, 21 May 2026 00:00:00 GMT AI News daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Hermes Agent's Honcho memory: Dialectic user modelling https://aikickstart.com.au/news/hermes-agent-honcho-memory-dialectic-modelling https://aikickstart.com.au/news/hermes-agent-honcho-memory-dialectic-modelling How Honcho's unique approach to memory creates agents that don't just remember facts but understand the evolution of their relationship with users. Wed, 20 May 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Building agents with Langflow: Step-by-step tutorial https://aikickstart.com.au/news/building-agents-langflow-step-by-step-tutorial https://aikickstart.com.au/news/building-agents-langflow-step-by-step-tutorial A hands-on tutorial for building your first AI agent in Langflow, from blank canvas to deployed API, no coding required. Tue, 19 May 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) The future of open source AI agents: What's next? https://aikickstart.com.au/news/future-open-source-ai-agents-whats-next https://aikickstart.com.au/news/future-open-source-ai-agents-whats-next From multi-agent orchestration to agent marketplaces to AI-native operating systems, we explore where open-source AI agents are headed in 2026 and beyond. Mon, 18 May 2026 00:00:00 GMT AI News daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Contributing to nanochat: Karpathy's educational vision https://aikickstart.com.au/news/contributing-to-nanochat-karpathy-educational-vision https://aikickstart.com.au/news/contributing-to-nanochat-karpathy-educational-vision How Andrej Karpathy's educational philosophy shapes nanochat's contribution culture and why 55,000 developers have bought into the vision. Sun, 17 May 2026 00:00:00 GMT AI News daniel.fleuren@aikickstart.com.au (Daniel Fleuren) The complete open source AI stack: 2026 edition https://aikickstart.com.au/news/complete-open-source-ai-stack-2026-edition https://aikickstart.com.au/news/complete-open-source-ai-stack-2026-edition Our definitive guide to building production AI systems entirely with open-source tools, from training to deployment to monitoring. Sat, 16 May 2026 00:00:00 GMT AI News daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Hermes vs OpenClaw vs OpenHuman in 2026 https://aikickstart.com.au/news/hermes-vs-openclaw-vs-openhuman-2026-comparison https://aikickstart.com.au/news/hermes-vs-openclaw-vs-openhuman-2026-comparison Three open-source agent frameworks have split into distinct philosophies. We put Hermes, OpenClaw and OpenHuman head-to-head on benchmarks and pricing. Mon, 15 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) How the Hermes Agent Learning Loop Works https://aikickstart.com.au/news/hermes-agent-learning-loop-deep-dive https://aikickstart.com.au/news/hermes-agent-learning-loop-deep-dive Inside Nous Research's self-improving agent runtime: the dialectic memory, FTS5 session search and feedback loops that make Hermes agents better over time. Sun, 14 Jun 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) OpenClaw Audit: CVE-2026-25253, 341 Bad Skills https://aikickstart.com.au/news/openclaw-security-audit-cve-2026-25253-and-341-malicious-skills https://aikickstart.com.au/news/openclaw-security-audit-cve-2026-25253-and-341-malicious-skills The Koi Security audit exposed critical flaws in OpenClaw. We break down the command injection bug, the malicious skills, and the foundation's response. Sat, 13 Jun 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) OpenHuman's Memory Trees: Technical Architecture Explained https://aikickstart.com.au/news/openhuman-memory-trees-architecture https://aikickstart.com.au/news/openhuman-memory-trees-architecture How TinyHumans.ai packs a lifetime of digital context into an Obsidian-style Markdown wiki, with its Neocortex base and screen intelligence pipeline. Fri, 12 Jun 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) ; embeddings: Float32Array; // For semantic search created: Date; modified: Date; parent?: string; // Tree reference children?: string[]; } Compression and the Subconscious Loop: Raw context piles up fast, and left alone it would bury any knowledge base. OpenHuman's **Subconscious** is a background self-learning loop that keeps compressing the Memory Trees. According to the maker and early reviews, it runs on a few time horizons: **Hourly**: Merge duplicate entities, resolve aliases, update relationship graphs. **Daily**: Generate daily summaries, prune low-signal observations, promote high-signal patterns. **Weekly**: Produce weekly reflection documents that surface recurring themes, forgotten commitments, and emerging priorities. (The Subconscious loop and daily summarisation are documented; the exact hourly/daily/weekly cadence above is described by the article rather than confirmed verbatim in the docs.) Compression leans on a stack of summarisation models. Small local models do the routine merging. Larger models, routed through the multi-model subscription, take on the harder synthesis. What you end up with is a tree where the recent leaves stay detailed and older branches get folded down into summarised trunk documents. Neocortex: Local Knowledge Base: Neocortex is the storage and search engine behind the Memory Tree. It [supports up to a billion tokens locally](https://dev.to/neocortexdev/i-am-building-the-first-ai-agent-with-big-data-capabilities-70e) and runs a [hybrid search](https://dev.to/neocortexdev/i-am-building-the-first-ai-agent-with-big-data-capabilities-70e): BM25 for exact matches, dense embeddings for semantic similarity, and graph traversal for relationship queries. You ask in plain language and it translates the question into a structured graph query: "What did I say about the billing migration last week?" That resolves to a filtered walk through conversation nodes, restricted by date, matching the entities "billing" and "migration," then ranked by recency and how strongly the relationships connect. Tauri and Distribution: OpenHuman ships as a [Tauri desktop app](https://github.com/tinyhumansai/openhuman) with native builds for macOS (DMG) and Windows (the GitHub docs list an MSI installer rather than a plain EXE). Picking Tauri over Electron reportedly keeps the binary under 15 MB and idle memory under 200 MB, though those specific figures aren't confirmed in the official release notes or docs. The Rust backend handles screen capture, file system watching, and the Neocortex search engine. The React frontend draws the Memory Tree UI and the desktop mascot. One Subscription, Multi-Model Routing: Plenty of competitors bill per model or per token. OpenHuman uses a single subscription that covers [multi-model routing](https://dev.to/neocortexdev/i-am-building-the-first-ai-agent-with-big-data-capabilities-70e) instead. The system picks the cheapest model that can do the job: local models for simple classification, cloud models for harder synthesis, premium models only when the task earns it. The auto-fetching integrations and the Subconscious loop keep running in the background, so the Memory Tree stays current without you prompting it. If you want to look under the hood yourself, the [GitBook getting-started guide](https://tinyhumans.gitbook.io/openhuman/overview/getting-started) and the [project releases](https://github.com/tinyhumansai/openhuman/releases) are the places to start.]]> Claude Code Plan Mode: The Senior Engineer's Workflow https://aikickstart.com.au/news/claude-code-plan-mode-senior-engineer https://aikickstart.com.au/news/claude-code-plan-mode-senior-engineer Plan Mode makes Claude Code propose a plan before writing code. Here's how senior engineers use that pause to break down big changes and hold quality. Thu, 11 Jun 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) /plan Refactor the authentication middleware to use JWT instead of sessions ## Analysis The auth middleware spans 3 files with 14 dependencies. Tests cover 67% of paths. Session handling is referenced in 23 files across 2 services. ## Task Decomposition 1. Extract session interface to abstract auth provider (low risk) 2. Implement JWT provider with backward-compatible session fallback (medium risk) 3. Update middleware to route through new provider (medium risk) 4. Add JWT secret rotation mechanism (medium risk) 5. Update all 23 call sites (high risk - many edge cases) 6. Expand test coverage to 90%+ (medium risk) ## Identified Risks - Risk #1: Rolling deployment requires both session and JWT active - Risk #2: 6 integration tests depend on session-specific behaviour - Risk #3: Mobile clients may not handle JWT expiry gracefully ## Estimated effort: 4-6 hours Why Senior Engineers Prefer It: Newer developers tend to ask Claude Code to "just fix it." Engineers who have been burned know that charging into changes on a complex system creates debt. Plan Mode bakes in the discipline that experience teaches: understand the problem, map the territory, name the risks, then write the code. The approval gate is the part that matters. Autonomous modes can rewrite a dozen files before you notice they took a wrong turn. Plan Mode stops at the line between planning and execution. You can reject a plan, ask for changes, or approve it with conditions, "skip step 4, we handle rotation in the gateway layer." Integration with Sub-Agents: Plan Mode pairs well with [Claude Code's sub-agent system](https://www.anthropic.com/news/claude-opus-4-8). A complex plan can spin off specialised sub-agents, one for test generation, one for documentation, one for migration scripts, while a coordinator holds the overall plan and hands out the work. With Opus 4.8's Dynamic Workflows, Claude can [plan the work and then run hundreds of parallel subagents in a single session](https://www.anthropic.com/news/claude-opus-4-8), with the coordinator resolving conflicts at the merge points. Anthropic ships that capability as a research preview, aimed at codebase-scale migrations from kickoff to merge. # Trigger Plan Mode claude /plan "your complex task here" # Or prefix any prompt claude "plan first: migrate from REST to GraphQL" When Not to Use Plan Mode: For a task under five files with a clear scope, Plan Mode is overhead you do not need. Direct mode, where Claude Code writes code straight away, is faster for bug fixes, small refactors, and adding a field to a data model. The skill is knowing which mode fits the job. Plan Mode earns its keep when the change is bigger than you can hold in your head at once, guides tend to suggest reaching for it when a change touches three or more files or cannot be summed up in a single sentence. Pricing Context: Worth clearing up: Plan Mode is not a paid extra. It is a built-in Claude Code feature, available on individual Pro and Max plans as well as team seats. The $100 figure people quote is the [Team Premium seat price, $100 per seat per month on annual billing, $125 month-to-month, with a five-seat minimum](https://support.claude.com/en/articles/9266767-what-is-the-team-plan). Where the spend makes sense is the same calculation any senior engineer runs: tool cost against the cost of a production incident. On the model side, [Opus 4.8 is around four times less likely than its predecessor to let flaws in code it wrote pass unremarked](https://www.anthropic.com/news/claude-opus-4-8), which is the kind of number that matters more than the seat price. Some teams report that Plan Mode cuts "Claude broke staging" rollbacks by something like 60% on complex tasks compared with direct mode, though that figure is anecdotal and not backed by any published study.]]> Claude Code Hooks: Advanced Agentic Coding Patterns https://aikickstart.com.au/news/claude-code-hooks-advanced-agentic-patterns https://aikickstart.com.au/news/claude-code-hooks-advanced-agentic-patterns Hooks turn Claude Code into a proactive agent. Build pre-commit validation, auto-documentation and architectural guardrails that fire automatically. Wed, 10 Jun 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) 3 or test_coverage_delta < 0" actions: - "generate diff summary in conventional commit format" - "identify untested paths in modified code" - "suggest test cases for uncovered paths" - "check for breaking changes in public APIs" Pattern 5: Sub-Agent Orchestration: The most ambitious pattern hands follow-on work to specialised sub-agents. When a particular file changes, each sub-agent picks up one piece of the cleanup. This leans on Opus 4.8's [Dynamic Workflows](https://www.axios.com/2026/05/28/anthropic-opus-release-mythos), which Anthropic introduced for running large numbers of parallel sub-agents in a single session: subagent_orchestration: event: file_save pattern: "src/schema/**/*.graphql" actions: - "spawn subagent: generate TypeScript types from schema changes" - "spawn subagent: update client query hooks" - "spawn subagent: regenerate mock data for tests" - "await all: run integration tests for affected queries" Worth noting: Opus 4.8 is real and shipped on 28 May 2026 with Dynamic Workflows. The claim that the hooks system itself was specifically "refined through Opus 4.8" is not something the sources confirm; hooks have evolved across several Claude Code releases on their own track, separate from any one model version. Simon Willison's [write-up of Opus 4.8](https://simonwillison.net/2026/May/28/claude-opus-4-8/) covers what actually shipped. Debugging Hooks: Here the original article goes badly off the map, so read this section as a correction. It refers to a `claude hooks trace --last` command and a `claude hooks test ` dry run: # Show hook execution trace for last session claude hooks trace --last # Show hooks that would trigger for a specific file (dry run) claude hooks test src/api/users.ts Those commands do not exist. Real hook debugging uses the interactive `/hooks` menu, which is a read-only browser of the hooks you have configured, plus the `--debug` flag for verbose logging when a hook misbehaves. That is where you find out whether the problem is in event detection, the condition, or the action. The diagnostic instinct in the original is right; the specific commands are invented. Performance Considerations: Hooks add time to whatever event triggers them. A save hook that type-checks the whole project will make every save feel slow. The fix is to scope conditions tightly and use incremental checks. The article also mentions a `priority` field for ordering and a `blocking: false` option for running non-critical hooks asynchronously, but as noted above, those specific fields are unconfirmed in the official reference, so test before you depend on them. The bigger point holds up even after the syntax corrections. The interesting move with hooks is that the assistant stops waiting to be asked. It watches what happens, checks it against your team's standards, and acts. Get that right and the tool you invoke turns into the environment you work inside. Just build it on the [real config format](https://code.claude.com/docs/en/hooks), not the one in the marketing examples.]]> Multi-Agent Orchestration: Running 10 Agents That Beat 1 https://aikickstart.com.au/news/multi-agent-orchestration-10-agents-beat-1 https://aikickstart.com.au/news/multi-agent-orchestration-10-agents-beat-1 Why a coordinator with nine specialised sub-agents beats one big model. Real patterns from Claude Code's Dynamic Workflows, Hermes and OpenClaw. Tue, 09 Jun 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) The Pi Coding Agent: Claude Code's First Real Competitor https://aikickstart.com.au/news/the-pi-coding-agent-claude-code-s-first-real-competitor https://aikickstart.com.au/news/the-pi-coding-agent-claude-code-s-first-real-competitor Inflection's Flow built a terminal coding agent that rivals Claude Code. We compare Pi's context management, tool use and pricing against Anthropic's. Mon, 08 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Google's Agents CLI: Shipping Agents from the Command Line https://aikickstart.com.au/news/google-agents-cli-shipping-from-command-line https://aikickstart.com.au/news/google-agents-cli-shipping-from-command-line Google's Agents CLI pairs command-line tooling with a skills framework so deploying an agent is as simple as `gcloud agents deploy`. Here's how it works. Sun, 07 Jun 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Agent Sandboxes: Isolating AI Agents for Safety https://aikickstart.com.au/news/agent-sandboxes-isolating-ai-agents-safety https://aikickstart.com.au/news/agent-sandboxes-isolating-ai-agents-safety Once agents get filesystem, network and shell access, sandboxing is non-negotiable. We compare container, VM and capability isolation with real benchmarks. Sat, 06 Jun 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Agent Memory: Honcho vs Files vs Trees https://aikickstart.com.au/news/agent-memory-systems-honcho-vs-files-vs-trees https://aikickstart.com.au/news/agent-memory-systems-honcho-vs-files-vs-trees Compare three agent memory architectures shaping 2026: Honcho dialectic user modelling, OpenClaw file journals, and OpenHuman knowledge trees. Fri, 05 Jun 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) The 3-Agent Stack: OpenClaw + Hermes + OpenHuman Together https://aikickstart.com.au/news/the-3-agent-stack-openclaw-hermes-openhuman https://aikickstart.com.au/news/the-3-agent-stack-openclaw-hermes-openhuman The best engineers don't pick one agent framework, they run all three. Here's how to wire OpenClaw messaging, Hermes' runtime and OpenHuman context. Thu, 04 Jun 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Claude Code Task System: Anti-Hype Agentic Coding https://aikickstart.com.au/news/claude-code-task-system-anti-hype https://aikickstart.com.au/news/claude-code-task-system-anti-hype How Claude Code Task System uses hierarchical decomposition and state persistence to keep agents reliable on long, messy real-world projects. Wed, 03 Jun 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Sub-Agents That Build Themselves: Advanced Patterns https://aikickstart.com.au/news/sub-agents-that-build-themselves https://aikickstart.com.au/news/sub-agents-that-build-themselves Self-building sub-agents grade their own work and spawn better versions of themselves. The real patterns for Claude Code, Hermes and OpenClaw. Tue, 02 Jun 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) 10% failure rate", "analyse failure patterns for each", "generate config variants with adjusted prompts/tools/models", "A/B test variants on synthetic tasks", "deploy winning variant if improvement >5%" ] } ] } This takes more hand-assembly than Claude Code or Hermes, but it runs. The point worth keeping is that self-improvement does not need native platform support. It needs structured evaluation and a configuration space you can search. The failure-rate threshold (>10%) and improvement threshold (>5%) above are example values, not numbers from any source. Pattern 4: Recursive Self-Building: The most advanced pattern is recursive: a meta-agent that improves not only the task-specific sub-agents but also its own evaluation and generation strategies. This one is, by the author's own admission, theoretical for production use. Experiments with Claude Code's [Opus 4.8](https://www.anthropic.com/news/claude-opus-4-8) (a real model, released 28 May 2026) are reported to show promising results, though that result is unconfirmed and not backed by a public source. In recursive self-building, the meta-agent holds a model of its own reasoning. When it notices its evaluation criteria are poorly calibrated (say, optimising for test coverage while missing bug detection), it updates them. When it notices its generation strategies are too cautious (searching too small a configuration space), it widens them. The obvious danger is runaway optimisation. Without solid guardrails, an agent that improves itself recursively could chase metrics that are easy to measure while quietly losing the quality those metrics were meant to stand in for. Human oversight stays essential. Guardrails for Self-Building Agents: Any self-building agent system needs these guardrails: **Regression tests**: New configurations must not break tasks that previously passed **Diversity requirements**: The configuration space has to stay diverse so it does not converge too early **Human review gate**: Deployments touching production require human approval **Kill switches**: The ability to revert to a known-good configuration on the spot **Metric sanity checks**: Confirm that the optimised metrics still correlate with human judgement The Current State: Self-building agents are not autonomous yet. They are assistive. They search the configuration space faster than a person can, surface patterns a person might miss, and suggest improvements a person then reviews and approves. The line between "suggests improvements" and "deploys them without asking" is where human judgement currently sits. That line is moving.]]> Context Engineering: The New Vibe Coding https://aikickstart.com.au/news/context-engineering-new-vibe-coding https://aikickstart.com.au/news/context-engineering-new-vibe-coding Why context engineering is replacing vibe coding, and how giving agents the right files, rules, and limits beats writing clever prompts. Mon, 01 Jun 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) 60%) **Revision count**: average back-and-forth turns to reach completion (target: <3) **Constraint compliance**: the share of explicit constraints respected in the output (target: >95%) **Convention alignment**: the share of output that matches team conventions (target: >90%) Engineers who put the work into context engineering reportedly see something like 40-60% fewer revision cycles than they did with vibe coding, though that figure reads as an estimate rather than a measured result from any published source. The idea, at least, is straightforward: time spent gathering and structuring context up front gets paid back in fewer rounds of fixing things. Context Engineering vs. Prompt Engineering: Prompt engineering tunes the query. Context engineering tunes the database. Both count, but context tends to win out, for a few reasons: A perfect prompt with thin context still fails An average prompt with strong context usually lands Context carries across many prompts; a prompt is tied to one task The agents getting the most attention in 2026, Claude Code with its Task system, Hermes paired with Honcho, and [OpenHuman with its Memory Trees](https://tinyhumans.gitbook.io/openhuman/features/obsidian-wiki/memory-tree) ([tinyhumansai/openhuman](https://github.com/tinyhumansai/openhuman)), are at heart context engines. Their job is to gather, structure, and surface the right context at the right moment. The engineers getting the best results are the ones who have worked this out and put their effort there.]]> Tool Calling Mastery: Long Chains of Correct Calls https://aikickstart.com.au/news/tool-calling-mastery-long-chains https://aikickstart.com.au/news/tool-calling-mastery-long-chains Elite agentic engineers build tool chains that stay correct across dozens of sequential calls. Here is how to make long chains reliable. Sun, 31 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) 0, "Migration must affect at least one table" # Verify no destructive operations without explicit flag assert not (output.has_drop_table and not output.force_flag), "DROP TABLE requires --force flag" def validate_api_response(output): assert output.status in [200, 201, 204], f"Unexpected status: {output.status}" assert output.content_type == "application/json", "Expected JSON response" assert output.body is not None, "Empty response body" Hermes stores its skills in the [agentskills.io](https://github.com/agentskills/agentskills) format, an open standard where a skill is just a folder with a SKILL.md. The article's claim that the spec includes output schemas enforcing these validations automatically goes further than the public spec, which describes the standard as deliberately tiny (metadata plus instructions). OpenClaw, a self-hosted agent framework with its own AgentSkill system, reportedly carries a comparable validation layer, though that specific capability isn't corroborated by [available write-ups](https://www.digitalocean.com/resources/articles/what-are-openclaw-skills) and reads as an editorial assertion. Pattern 4: Compensating Transactions: For destructive operations, build compensating transactions: undo steps that reverse a tool call if the chain fails later. # Migration chain with compensating transactions chain = [ ToolCall("create_backup", rollback="restore_backup"), ToolCall("create_new_table", rollback="drop_new_table"), ToolCall("dual_write", rollback="disable_dual_write"), ToolCall("backfill", rollback="clear_backfill"), ToolCall("switch_read", rollback="switch_read_back") ] try: execute_with_rollback(chain) except ChainFailure as e: # Rollback all completed steps in reverse order for completed in reversed(e.completed_steps): if completed.rollback: execute(compensated.rollback) Pattern 5: Human-in-the-Loop Gates: For critical or irreversible operations, add a human approval gate. The agent shows what it plans to do, a person approves or changes it, and the chain continues. It costs you some latency and it prevents the kind of failure you can't walk back. # Human approval gate if tool_call.risk_level == "high": approval = request_human_approval( action=tool_call.description, impact=tool_call.impact_analysis, rollback=tool_call.rollback_description ) if not approval.granted: chain.skip_or_alternative(tool_call, approval.suggestion) Building Reliable Chains: Rules of Thumb: **Never chain more than 10 calls without a checkpoint.** Error accumulation makes longer chains unreliable once you drop verification. **Always validate outputs semantically.** Checking that the JSON parses is not enough. Confirming that values sit in expected ranges and required fields are present is what catches the real errors. **Make dependencies explicit.** Implicit dependencies through shared state are the most common way chains break. **Implement rollbacks for destructive operations.** Assume the chain will fail and plan the recovery up front. **Parallelise where you can.** Dependency graph execution cuts total latency and isolates failures. Long chains of correct tool calls are what separate agent demos from agent production systems. The patterns above aren't theoretical. They show up, by various accounts, in the agent deployments that hold up best under real load.]]> The OpenClaw to Hermes Migration: Step-by-Step https://aikickstart.com.au/news/openclaw-to-hermes-migration-guide https://aikickstart.com.au/news/openclaw-to-hermes-migration-guide Moving from OpenClaw to the Hermes learning runtime takes planning. The practical migration path, the built-in tool, and manual steps for tricky setups. Fri, 29 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) skills_audit.json # Check which messaging channels are active openclaw channels list > channels_audit.json # Export memory files cp MEMORY.md hermes_migration/ cp -r .openclaw/journal/ hermes_migration/journal/ # Document custom configurations openclaw config export > config_backup.json What you are looking for: Custom skills that aren't published on agentskills.io Channel-specific workflows, like Discord bot commands Cron-scheduled sub-agents Integrations with external services Phase 1: Run the Migration Tool: Hermes ships [`hermes claw migrate`](https://hermes-agent.nousresearch.com/docs/guides/migrate-from-openclaw) for exactly this transition. # Install Hermes pip install hermes-agent # Run the migration hermes claw migrate \ --source ~/.openclaw \ --target ./hermes_project \ --import-memory \ --import-channels \ --import-skills According to the official docs, the migration tool handles three things. The exact internal breakdown below is illustrative, but it matches the documented behaviour: **Memory conversion**: `MEMORY.md` and journal files are turned into [Honcho dialectic memory](https://github.com/NousResearch/hermes-agent/blob/main/website/docs/user-guide/features/honcho.md) entries. Each journal entry becomes a conversation with its context attached. **Channel migration**: Discord, Slack, Telegram, and other channel configs are mapped onto Hermes' messaging adapters. **Skill mapping**: OpenClaw AgentSkills are matched to Hermes tool equivalents where one exists. Anything without a direct match gets flagged for you to review by hand. Phase 2: Review and Remediate: The tool gives you a report of what it sorted out on its own and what still needs you. The numbers below are example output, not figures from a real run: Migration Report ================ Memory entries: 1,247 imported (100%) Channels: 5 imported, 2 require manual config Skills: 23 mapped automatically, 8 flagged for review Sub-agents: 3 cron schedules migrated Warnings: - Custom skill "internal-deploy" has no Hermes equivalent - Telegram webhook URL needs updating - Discord bot permissions may need re-authorisation Manual Skill Migration When a skill doesn't map on its own, you have three options: **Find an equivalent on [agentskills.io](https://github.com/VoltAgent/awesome-openclaw-skills)**: Look for a community-maintained alternative. **Port the skill**: Convert the Node.js skill to Python for Hermes. **Keep OpenClaw for that one function**: Run both systems through the transition. # Porting an OpenClaw skill to Hermes # OpenClaw version (Node.js) # module.exports = { onMessage: async (msg) => { ... } } # Hermes version (Python) from hermes.tools import tool @tool("deploy_service") async def deploy_service(environment: str, version: str) -> dict: """Deploy service to specified environment.""" # Ported logic from OpenClaw skill result = await run_deploy_script(environment, version) return {"status": result.status, "url": result.url} Channel Re-Authorisation Your messaging channels need re-authorising, because Hermes connects with its own bot credentials rather than OpenClaw's. # Discord hermes channels discord connect \ --bot-token $DISCORD_BOT_TOKEN \ --guild-id $DISCORD_GUILD_ID # Slack hermes channels slack connect \ --app-token $SLACK_APP_TOKEN \ --bot-token $SLACK_BOT_TOKEN # Telegram hermes channels telegram connect \ --api-token $TELEGRAM_API_TOKEN \ --webhook-url https://your-hermes-instance/webhook/telegram Phase 3: Parallel Operation: Run both systems side by side for a while. Two weeks is a sensible window. Move channels across one at a time rather than all at once. Phase 4: Cutover: Once every channel is working on Hermes: Disable OpenClaw's bot accounts Point OpenClaw webhooks at Hermes Update any docs that still reference OpenClaw commands Hang on to the OpenClaw config backup for 30 days Cost Impact: The figures below are estimates to give you a rough sense of the trade-off, not published numbers. Real hosting cost depends on the VPS or serverless provider you pick (Hermes supports VPS, Docker, Modal, and Daytona). Hosting: $0-24/mo: ~$5/mo: Lower Token costs: Similar: Similar: Neutral Setup time: N/A: 4-8 hours: Upfront cost Maintenance: Higher (security): Lower: Savings over time The upfront hours are real, but for most teams the move pays back through less security firefighting and an agent that gets better at the job over time.]]> Harness Engineering: What Separates Top Agentic Engineers https://aikickstart.com.au/news/harness-engineering-top-agentic-engineers https://aikickstart.com.au/news/harness-engineering-top-agentic-engineers Why the best agentic engineers win on harness engineering, building the constraints and feedback loops that keep AI agents reliably useful. Thu, 28 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) ` error handling. 2. Context Harnesses Elite engineers put real effort into context engineering (article 15). They maintain `CONVENTIONS.md`, keep `MEMORY.md` current, and structure their prompts to include all five layers of context. A typical setup looks like this: `CONVENTIONS.md`: Team coding standards (updated monthly) `ARCHITECTURE.md`: System design documentation `DECISIONS.md`: Record of architectural decisions with rationale `.claude/hooks.yaml`: Automated quality enforcement `hermes memory import`: Historical session context 3. Verification Harnesses Average engineers verify agent output by hand. Elite engineers build verification pipelines instead: stages: - name: compile command: npm run build required: true - name: lint command: npm run lint required: true auto_fix: true - name: test command: npm test required: true coverage_threshold: 80 - name: typecheck command: npm run typecheck required: true - name: security_scan command: npm audit --audit-level=moderate required: true 4. Feedback Harnesses The best engineers close the loop. When an agent makes a mistake, they do not just fix it. They update the harness so it cannot happen again: Agent generated code with a race condition: add "check for race conditions" to constraints Agent missed an edge case: add the edge case to the test harness and context Agent used a deprecated API: update CONVENTIONS.md with the approved API list Agent violated architecture: add an architecture_review stage to the verification pipeline 5. Recovery Harnesses Production agents need a way out when something breaks: **Git-based recovery**: All agent changes go in branches, not direct commits **Database migrations**: Always reversible, with rollback tested **Feature flags**: Agent-deployed changes can be toggled off **Monitoring**: Alerts when agent activity exceeds normal patterns **Circuit breakers**: Agent paused automatically if the error rate spikes The Harness Engineering Mindset: The shift from coding to harness engineering is subtle, but it changes how you spend your day: Writes code directly: Designs systems that write code Reviews code manually: Builds automated review pipelines Fixes bugs individually: Updates harness to prevent bug class Optimises algorithms: Optimises agent context and constraints Measures lines of code: Measures agent success rate and rollback rate Values coding speed: Values harness reliability Measuring Harness Quality: The following thresholds are suggested benchmarks rather than measured industry standards, but they give you a sense of what good looks like. Elite harness engineers tend to track: **First-attempt success rate**: more than 60% of agent tasks complete without revision **Rollback rate**: under 5% of agent changes are rolled back **Constraint violation rate**: under 2% of outputs violate defined constraints **Time to recovery**: mean time to recover from agent failures under 30 minutes **Harness iteration rate**: how quickly constraints are updated after failures, under 24 hours The Future: Meta-Harnesses: The furthest expression of harness engineering is the meta-harness: a harness that improves itself. Systems like [Omnigent](https://github.com/omnigent-ai/omnigent) (article 20) analyse agent performance and suggest harness improvements automatically. A meta-harness does not replace the harness engineer. It amplifies them, surfacing patterns and recommendations that would take weeks to find by hand.]]> Omnigent: The Meta-Harness for Every Coding Agent https://aikickstart.com.au/news/omnigent-meta-harness-every-coding-agent https://aikickstart.com.au/news/omnigent-meta-harness-every-coding-agent Omnigent is a meta-harness that sits above Claude Code, Cursor, Hermes and OpenClaw, enforcing constraints, context and quality whatever agent runs. Wed, 27 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) --to # Show harness metrics omnigent metrics --since 7d These commands (`init`, `validate`, `sync`, `verify`, `context export`, `metrics`) do not match Omnigent's actual CLI and appear invented. If you want to try the real thing, the documented entry points are `omni setup`, `omnigent run`, `omnigent attach`, and `omnigent server start`, plus a local web UI on port 6767. Current State and Limitations: This account claims that as of June 2026 Omnigent is a specification plus a set of reference implementations rather than a single product, with a stabilising v1.0 draft spec and community-maintained adapters. That framing is not right. Omnigent shipped as a single open-source product from Databricks under Apache 2.0, with a CLI and a local web UI, not as a loose spec with community adapters. So the limitations listed below describe the imagined config-sync design, not the real release: **Not every agent feature fits the unified format.** Advanced Claude Code Hooks behaviour might still need native config. **Context sharing would be lossy.** Some agent-specific context (Honcho's dialectic model, for instance) does not translate cleanly. **Bi-directional sync invites conflicts** when the same setting gets changed in two files at once. Why Omnigent Matters: The honest version of the "why" still holds, even after stripping out the invented mechanics. The agent field is fragmenting. New agents arrive most months, each with its own format. Without something sitting above them, a team picks between two bad options: standardise on one agent and give up what the others do well, or keep maintaining parallel configs by hand. A meta-harness is meant to let you mix and match. Use one agent for heavy refactors, another for learning-intensive work, a third for quick edits, and keep a single consistent layer across all of them. That is where Omnigent is genuinely aiming, even if this particular write-up oversells how it gets there. The plausible future is not one agent that wins, but several agents run through one harness. One catch: the article it draws on never credits Databricks, who actually built and released the thing.]]> Loop Engineering: Building Self-Improving Agent Systems https://aikickstart.com.au/news/loop-engineering-self-improving-agent-systems https://aikickstart.com.au/news/loop-engineering-self-improving-agent-systems Self-improving agents are not magic, they are engineered feedback loops. How to design observation, evaluation, extraction, integration and decay. Tue, 26 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) dual_write -> backfill -> switch_read." **Anti-pattern extraction**: Patterns that correlate with failures. As an illustration, a rule of the form "avoid using eval() in skills" can be derived from audit data. (A real Koi Security audit of community skills did find hundreds of malicious entries, though the specific "100% of eval() usages were malicious" figure is unconfirmed and should not be read as a sourced statistic, per [MarkTechPost's coverage](https://www.marktechpost.com/2026/05/10/openclaw-vs-hermes-agent-why-nous-researchs-self-improving-agent-now-leads-openrouters-global-rankings/).) **Preference extraction**: User-specific preferences via Honcho dialectic user modelling ([Hermes Honcho memory docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/honcho)). A preference such as "user prefers functional patterns with confidence 0.91" is the kind of output this produces, shown here as an example rather than a real recorded value. Integration Mechanisms Extracted patterns are useless until they shape what the agent actually does next. Integration mechanisms include: **Prompt augmentation**: Adding successful patterns to system prompts **Tool preference ranking**: Biasing tool selection toward historically successful tools **Default parameter setting**: Using parameters that worked well in similar past tasks **Constraint generation**: Creating new constraints from identified anti-patterns Decay Schedules Without decay, an agent's knowledge only ever grows, and past a point that becomes a liability. One reported design uses power-law decay, where recent observations carry full weight, observations from a week ago carry half, and observations from a month ago carry a quarter, with low-activation patterns archived to cold storage after 30 days. Treat those specific numbers as an unconfirmed example: Hermes documents bounded, curated, cache-aware memory but does not publish this exact schedule. The principle holds even if your weights differ. Loop Types by Time Horizon: Seconds: Inline: Tool result: Adjust next tool choice based on output Minutes: Session: Task completion: Update preferences based on user corrections Hours: Daily: Scheduled job: Compress and integrate day's observations Days: Weekly: Weekly trigger: Archive obsolete patterns, generate summaries Weeks: Epoch: Manual or triggered: Major knowledge reorganisation Measuring Loop Quality: If you run one of these systems, track these metrics: **Learning velocity**: How much useful knowledge is extracted per unit time **Retention accuracy**: Percentage of extracted knowledge that remains relevant after 30 days **User correction trend**: Corrections per session should fall over time **First-attempt success rate**: Should climb as the loop learns user preferences **Knowledge freshness**: Percentage of active knowledge that is less than 30 days old As a rough rule of thumb (not a published benchmark), a well-engineered learning loop should lift first-attempt success rate by something like 15-25% over the first month of operation. If your loop shows no measurable improvement at all, the fault usually sits in the evaluation function, the extraction strategy, or the integration mechanism.]]> Claude Code vs Cursor vs Copilot Compared https://aikickstart.com.au/news/claude-code-vs-cursor-vs-copilot-compared https://aikickstart.com.au/news/claude-code-vs-cursor-vs-copilot-compared Claude Code, Cursor, and GitHub Copilot compared on workflow, pricing, and capability, so you pick the right coding assistant for your team. Mon, 25 May 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Agent Orchestration: Coordinator, Router, Specialist https://aikickstart.com.au/news/agent-orchestration-patterns-coordinator-router-specialist https://aikickstart.com.au/news/agent-orchestration-patterns-coordinator-router-specialist A practical guide to three multi-agent orchestration patterns, when to reach for the Coordinator, the Router, or deep Specialist agents. Sun, 24 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Router (classifies and dispatches) ├── Code Agent (implementation tasks) ├── Test Agent (test generation and validation) ├── Review Agent (code review and quality) └── Docs Agent (documentation generation) OpenClaw's sub-agent setup fits this shape. A parent agent passes messages to the right child agent. Worth a caveat here: OpenClaw's own [multi-agent docs](https://docs.openclaw.ai/concepts/multi-agent) describe routing as binding-based (it matches on peer, thread, or role, with the most specific match winning) rather than the looser "content analysis" framing you sometimes see. OpenHuman reportedly takes a comparable line with its [multi-model routing](https://medium.com/@neonmaxima/openhuman-follows-openclaws-rise-but-with-an-obsidian-brain-2fe4e21b7f2e), sending different request types to different models. **Best for**: High-volume settings with a wide mix of request types. Support bots, team assistants, CI/CD pipelines. **Trade-off**: With no shared state, individual agents can make choices that are sensible on their own but poor for the job as a whole. Pattern 3: The Specialist: The Specialist pattern is the most involved of the three. Several agents, each with real depth in one domain, work together through shared protocols. Every specialist keeps its own memory, tools, and standards for judging good work. They hand off to each other, push back, and critique each other's output. API Specialist <-> Database Specialist <-> Frontend Specialist | | | └------------------┴-----------------------┘ | Integration Tests Hermes builds this on its agentskills.io ecosystem. According to the project's own framing, specialist agents draw on independent [Honcho](https://hermes-agent.nousresearch.com/docs/user-guide/skills/optional/autonomous-ai-agents/autonomous-ai-agents-honcho) memory models while sharing skill signatures, though the per-specialist memory detail leans more on interpretation than on documented behaviour. The idea is that each one owns its patch: the API specialist knows REST design, the database specialist knows query optimisation, and they meet in the middle through shared schemas and contracts. **Best for**: Complex projects that need genuine depth across several areas at once. Platform engineering, full-stack work, system architecture. **Trade-off**: Heavy coordination cost. Specialists can disagree, and resolving that often needs a meta-coordinator sitting above them. Choosing the Right Pattern: Task complexity: Medium: Low-Medium: High Request diversity: Low: High: Medium Team size: Small: Large: Medium-Large Domain depth: Medium: Low: High Latency tolerance: High: Low: Medium Coordination overhead: Medium: Low: High Implementation with tmux: If you live in the terminal, Claude Code can run agents across [tmux panes](https://code.claude.com/docs/en/agent-teams), one agent per pane (this needs the `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` flag set and tmux installed). The illustrative commands below show the three patterns side by side. Note that these are conceptual examples rather than shipping CLI commands: in practice, Claude Code's agent teams are started by describing your teammates in plain language, not via a `claude multi-agent --pattern` subcommand. # Launch coordinator with 3 workers claude multi-agent --pattern coordinator --workers 3 # Launch router with 4 specialists claude multi-agent --pattern router --specialists code,test,review,docs # Launch specialist pattern with 3 domain experts claude multi-agent --pattern specialist --domains api,database,frontend Anti-Patterns to Avoid: **The recursive delegation spiral**: Agent A hands off to Agent B, which hands off to Agent C, which hands back to Agent A. Cap it with a maximum delegation depth. **The echo chamber**: Specialists harden each other's mistakes because nobody checks the work from the outside. Add a dedicated critic agent. **The coordination explosion**: Too many agents talking, nobody working. As a rough heuristic, some practitioners suggest watching the share of effort spent on coordination and keeping it modest (one rule of thumb floated is under 25%), though this is a working guideline rather than an established benchmark. **The single-model fallacy**: Using one model for every role. Coordinators usually need a large model; workers often do not. Match the model to the job. Multi-agent orchestration is not a numbers game. Piling on more agents does not buy you more capability. What pays off is the right agents, arranged sensibly, talking to each other in a way that suits the work. The three patterns here are well worn at this point, and the anti-patterns are the mistakes people keep making. Pick the one that matches your job, not the one that sounds most impressive.]]> Building an AI Second Brain: Architecture Deep Dive https://aikickstart.com.au/news/building-ai-second-brain-architecture https://aikickstart.com.au/news/building-ai-second-brain-architecture The six-layer architecture that turns raw digital exhaust into retrievable, actionable knowledge. Inside OpenHuman's Memory Trees and local-first model. Sat, 23 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Processing -> Storage -> Retrieval -> Synthesis -> Action Layer 1: Ingestion Ingestion captures data from every source you care about. OpenHuman ships with [118+ third-party integrations that auto-fetch every 20 minutes](https://github.com/tinyhumansai/openhuman), covering GitHub, GitLab, Linear, Notion, Slack, Discord, Gmail, Google Calendar, and more. The [desktop mascot adds screen intelligence](https://tinyhumans.gitbook.io/openhuman/features/mascot): what you are reading, what code you are writing, what documents you have open. Ingestion has to be: **Comprehensive**: Missing sources create blind spots **Real-time**: Stale data is less useful than fresh data **Non-intrusive**: It must not get in the way of your work **Respectful**: You control what gets captured and what does not Layer 2: Processing Raw data is useless without structure. Processing normalises, enriches, and connects: **Normalisation**: GitHub issues, Linear tickets, and Notion tasks become the same fundamental entity type **Entity extraction**: People, projects, technologies, and deadlines are identified and linked **Relationship mapping**: "This email references that GitHub issue which relates to this Linear ticket" **Sentiment analysis**: Flagging urgency, frustration, and excitement interface ProcessedEntity { id: string; source: IntegrationSource; type: EntityType; content: string; // Markdown entities: ExtractedEntity[]; relationships: Relationship[]; sentiment: SentimentScore; embeddings: Float32Array; timestamp: Date; } Layer 3: Storage OpenHuman's [Neocortex](https://github.com/tinyhumansai/neocortex) is marketed as storing up to 1 billion tokens locally, though the Neocortex repo's own spec cites accurate handling of over 10 million tokens, so treat the billion-token headline as a marketing figure rather than a benchmarked one. The author describes the storage as a hybrid approach: **BM25**: Exact text matching for precise retrieval **Dense embeddings**: Semantic similarity for conceptual search **Graph traversal**: Relationship queries ("what did Sarah say about the API?") **Hierarchical compression**: Recent data is detailed; old data is summarised Worth a caveat here: OpenHuman's docs confirm the [hierarchical summary trees and on-device embeddings](https://tinyhumans.gitbook.io/openhuman/features/obsidian-wiki/memory-tree), but the BM25 and graph-traversal mechanisms are this article's characterisation rather than documented features. The Memory Trees format itself is an Obsidian-style Markdown wiki: human-readable, version-controllable, and portable. You own your data. It lives on your machine, not in someone else's cloud. Layer 4: Retrieval Retrieval has to be fast, relevant, and contextual. The query "what was the decision about authentication?" should return: The decision document from DECISIONS.md Related Slack discussions The GitHub PR that implemented it Follow-up Linear tickets Your own notes from the meeting Retrieval quality is measured by [MRR (Mean Reciprocal Rank)](https://en.wikipedia.org/wiki/Mean_reciprocal_rank) and NDCG (Normalised Discounted Cumulative Gain). As an illustrative benchmark, a well-tuned second brain might aim for MRR > 0.7 on common queries, though that threshold is an author's figure rather than a published OpenHuman or industry number. Layer 5: Synthesis Synthesis is the part that earns its keep. The second brain does not just find information, it generates insights: **Weekly reflections**: "You spent 40% of your time on billing this week" **Connection surfacing**: "This problem resembles one you solved three months ago" **Priority triage**: "Three deadlines are approaching; here is the optimal order" **Knowledge gaps**: "You have been mentioned in 12 threads but have not responded to 5" OpenHuman's [Subconscious loop](https://dev.to/neocortexdev/i-am-building-the-first-ai-agent-with-big-data-capabilities-70e) handles synthesis continuously in the background, working away while you stop typing. The cadence is reportedly hourly merges, daily summaries, and weekly reflections, though that exact schedule was not confirmed verbatim in the documentation, and it runs without you having to ask. Layer 6: Action The whole point of a second brain is action. Information that does not change what you do is just trivia: **Inline autocomplete**: Suggesting relevant code based on your research **Meeting preparation**: Summarising context before a Google Meet **Follow-up reminders**: Surfacing commitments you have forgotten **Cross-reference linking**: Automatically linking related documents Building Your Own: You do not need OpenHuman to build a second brain. The architecture can be implemented with open-source tools: Ingestion: n8n or Huginn for integrations Processing: Python scripts with spaCy/Transformers Storage: SQLite + FTS5 + pgvector (or Chroma for embeddings) Retrieval: Custom search with hybrid ranking Synthesis: Periodic LLM calls (Claude API, OpenRouter) Action: Webhooks to your tools These are all real, widely used tools, so the stack is sound. But the integration effort is substantial. OpenHuman's value is not the architecture, it is the execution: 118+ integrations working out of the box, a polished desktop app, and the Subconscious loop running continuously without configuration. Privacy Considerations: A second brain knows everything. That is its power and its risk: OpenHuman stores everything locally. No cloud required. Screen intelligence processes on-device. Screenshots never leave your machine. Third-party integrations use OAuth, and the tokens are reportedly held in the macOS/Windows keychain, though that specific storage detail was not confirmed in the documentation. Markdown exports let you inspect exactly what is stored. The local-first model is a deliberate privacy choice. A cloud-based second brain would be more powerful (unlimited storage, always available, team sharing) but would mean trusting a third party with your entire digital life. OpenHuman bets that most users will pick privacy over convenience. The second brain is not a settled product category yet. It is an aspiration. OpenHuman is the closest implementation I have seen, and it ships updates often, with the project moving past v0.57 by mid-2026. The author predicts that within 12 months "second brain" will be as common a term as "code editor", which is a forecast worth noting rather than a sure thing.]]> The Future of IDEs: Will Agents Replace Editors? https://aikickstart.com.au/news/future-of-ides-will-agents-replace-editors https://aikickstart.com.au/news/future-of-ides-will-agents-replace-editors Whether AI agents will replace the IDE or absorb it, and how a new agent-led tool is reshaping how software actually gets built in 2026. Fri, 22 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Prompt Engineering for Agents: System Prompts That Work https://aikickstart.com.au/news/prompt-engineering-for-agents-system-prompts https://aikickstart.com.au/news/prompt-engineering-for-agents-system-prompts System prompts are the highest-leverage fix in agentic coding. A six-section framework that lifts output quality across Claude Code, Hermes and OpenClaw. Thu, 21 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) 0.8, f"Failed on {task}: {score}" Prompt Length Trade-offs: A longer prompt carries more context but eats into your token budget. The practical ceiling is the model's context window minus the space the actual task needs. With [Claude Opus 4.8](https://www.anthropic.com/claude/opus), a roughly 2,000-token system prompt still leaves plenty of room for involved work. On smaller models, trim the prompt to 500-1,000 tokens by keeping the constraints and the output format and cutting the rest. System prompt engineering is one of the highest-leverage moves available in agentic coding. Iterating costs nothing, a test cycle takes minutes, and teams that put the work in commonly report a noticeable lift in output quality. It's worth your time here before you reach for a bigger model or bolt on more tools.]]> Agent Evaluation: How to Measure Agent Performance https://aikickstart.com.au/news/agent-evaluation-measure-performance https://aikickstart.com.au/news/agent-evaluation-measure-performance The four-level measurement pyramid that separates reliable agent deployments from hopeful experiments, from component metrics to business impact. Wed, 20 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) 95% Context relevance: % of retrieved context actually used: >80% Prompt adherence: % of constraints followed in output: >90% Hallucination rate: % of outputs containing fabricated information: <2% Format compliance: % of outputs matching requested format: >95% These need automated evaluation, usually model-based. Claude Code's built-in telemetry covers some of them: with OpenTelemetry turned on, it emits token usage, cost, session counts, and tool-execution events you can mine for component data ([Anthropic Claude Code docs, Monitoring usage](https://docs.anthropic.com/en/docs/claude-code/monitoring-usage)). For retrospective digging, Hermes' FTS5 session database lets you full-text search across past sessions and pull patterns out of old transcripts ([Nous Research Hermes Agent, Session Storage](https://hermes-agent.nousresearch.com/docs/developer-guide/session-storage)). Level 2: Technical Metrics: Technical metrics watch system health: Token usage per task: Average tokens consumed: Minimise Latency (p50/p95): Time to task completion: p50<60s, p95<300s Error rate: % of tasks ending in error: <5% Retry rate: % of tasks requiring human intervention: <20% Cost per task: Token cost + compute: Track and optimise Level 3: Task Outcomes: Task outcome metrics ask the question that matters: did the agent actually get the job done? Success rate: % of tasks completed without human fix: Human review First-attempt success: % correct on first try: Automated + spot check Code quality score: Composite of lint, test, review: Automated pipeline Regression rate: % of changes that break existing code: CI/CD Time saved: (Human estimate) - (Agent time): Self-report Level 4: Business Impact: Business impact metrics tie agent usage back to what the organisation actually cares about: Developer velocity: Story points or PRs per sprint Bug escape rate: Bugs found in production vs. development Developer satisfaction: Survey scores Time to resolution: Mean time to fix bugs or implement features Knowledge transfer speed: Time for new developers to become productive Evaluation Methodologies: Human Evaluation The gold standard, and expensive. Use it for: Calibrating your automated evaluators at the start Edge cases and task types you haven't seen before Final sign-off on production deployments Model-Based Evaluation Use a stronger model to grade a weaker model's output. For example, an Opus-class model can score the work of a faster Sonnet-class model. (One commonly cited version of this, that Claude Code internally uses Opus 4.8 to grade Sonnet 4.8 outputs, is unconfirmed: it has no public source, and "Sonnet 4.8" does not appear to be a released model. The current Sonnet is [Sonnet 4.6](https://www.anthropic.com/news/claude-sonnet-4-6); [Opus 4.8](https://www.anthropic.com/news/claude-opus-4-8) is real.) The approach scales well, but it inherits whatever biases the evaluator model carries. def model_evaluate(output, criteria, evaluator="opus-4.8"): prompt = f"Evaluate this output on {criteria}. Score 1-10. Explain." return claude.generate(prompt, model=evaluator) Reference-Based Evaluation Compare agent output against human-written reference solutions, using BLEU, [ROUGE](https://en.wikipedia.org/wiki/ROUGE_%28metric%29), or custom similarity metrics. It's only as good as the reference solutions you have, in quality and in coverage. Execution-Based Evaluation Run the generated code and see if it passes the tests. For coding tasks this is the most objective metric you'll get. The catch is that it leans entirely on the quality of your test suite. Building an Evaluation Suite: evaluation_suite/ ├── unit_tests/ # Does generated code compile and pass? ├── integration_tests/ # Does it work with the rest of the system? ├── regression_tests/ # Does it break anything? ├── quality_checks/ # Lint, format, complexity ├── reference_compare/ # Similarity to human-written solutions └── human_review/ # Manual quality assessment Run the full suite before you deploy any prompt or model change. Run component metrics continuously. Review business impact monthly. Red Flags: These patterns tell you the evaluation itself is broken: **Measuring proxy metrics**: "Lines of code generated" barely correlates with value **Cherry-picking examples**: Testing only on tasks you already know the agent handles well **No human baseline**: If you don't know how a person performs, the agent's numbers mean nothing **Static benchmarks**: Agent performance drifts, so evaluate continuously **Ignoring failure modes**: Counting wins without categorising the losses Agent evaluation isn't a one-off. It's an ongoing practice, and it decides whether your deployment gets better or worse over time. Teams that evaluate well ship with confidence. Teams that don't are just hoping.]]> The Cost of Agentic Coding: Real-World Pricing Analysis https://aikickstart.com.au/news/cost-of-agentic-coding-real-world-pricing https://aikickstart.com.au/news/cost-of-agentic-coding-real-world-pricing Agentic coding is not free. The real costs of API pricing, infrastructure, engineer time and rework, with a total cost example for a 5-person team. Tue, 19 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Agent Safety: Sandboxing, Approval Gates, and Human Review https://aikickstart.com.au/news/agent-safety-sandboxing-approval-gates-review https://aikickstart.com.au/news/agent-safety-sandboxing-approval-gates-review A three-pillar safety model for production agents, sandboxing, approval gates, and human review, with lessons from CVE-2026-25253. Mon, 18 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) 10 files modified: Notify, allow override Low: Single file edit, test addition: Log only Claude Code's [Plan Mode](https://code.claude.com/docs/en/common-workflows) is the most mature approval gate I have used. It reads the codebase, writes out a numbered plan of the files it will touch and the commands it will run, and refuses to change anything until you approve. You can edit the plan or cancel it first. Hermes offers [configurable approval gates](https://hermes-agent.nousresearch.com/docs/user-guide/docker) too: it can require manual sign-off before destructive commands, and generated code has to pass constraint checks (unit tests, file-size limits) before it runs. Treat the levels above as a starting template, not gospel. They are a sensible default, but you will tune them to your own risk appetite. Pillar 3: Human Review: Human review catches what automation misses: subtle bugs, work that technically passes but heads the wrong architectural direction, security holes that static analysis walks straight past. The trick is to make review fast, not bureaucratic. What works in practice: **Automated pre-review**: Run lint, tests, and security scans before a human sees the code **Diff-only review**: Show only what changed, with clear context **Risk-based routing**: High-risk changes go to senior engineers; low-risk changes can be self-merged **Review time limits**: Review within 4 hours or auto-approve with logging **Review feedback loops**: When reviewers catch agent bugs, update the harness The Three-Pillar Maturity Model: Level 1 (Basic): Container isolation: Plan Mode for complex tasks: All changes reviewed Level 2 (Intermediate): Capability-based + container: Risk-calibrated gates: Risk-based routing Level 3 (Advanced): VM-based + capability-based: Context-aware gates: Review sample + spot checks Level 4 (Elite): Defence-in-depth stack: Minimal gates, high trust: Trust-but-verify with audit This model and the thresholds that follow are my recommendation rather than an industry standard, so weigh them against your own data. Most teams should start at Level 1 and move up based on rollback rates. If your rollback rate sits below 2%, you can think about easing off the approval gates. If it climbs above 10%, tighten them. Agent-Specific Security Risks: Beyond ordinary software security, agents bring [their own set of risks](https://thehackernews.com/2026/02/researchers-find-341-malicious-clawhub.html): **Prompt injection**: Malicious input that overrides system instructions **Tool misuse**: Agent using a legitimate tool for unintended purposes **Information leakage**: Agent exfiltrating sensitive data through tool outputs **Goal misalignment**: Agent pursuing the literal goal in ways that violate implicit constraints **Supply chain via skills**: Malicious skills or dependencies, the kind Koi Security uncovered in the ClawHavoc campaign Each one needs its own mitigation: Prompt injection: Input validation, prompt boundaries, output encoding Tool misuse: Capability-based restrictions, tool-specific guards Information leakage: Network restrictions, output filtering, audit logging Goal misalignment: Constraint specification, approval gates, human oversight Supply chain: Skill signing, sandboxing, audit (the Koi Security model) Incident Response: When an agent causes a security incident: **Contain**: Disable the agent, revoke its credentials **Assess**: Determine scope of impact (what did it access, modify, or exfiltrate) **Recover**: Roll back changes, rotate secrets, patch vulnerabilities **Analyse**: Root cause analysis. Was it a bug, a malicious input, or a design flaw? **Remediate**: Update harness, add constraints, improve monitoring **Document**: Incident report for the team and, if severe, the community Agent safety is not about eliminating risk. It is about keeping risk in line with the value the agents return. The teams that deploy agents safely are the ones that treat safety as something they keep doing, not a box they tick once.]]> Multi-Model Routing: Using the Right Model for Each Task https://aikickstart.com.au/news/multi-model-routing-right-model-right-task https://aikickstart.com.au/news/multi-model-routing-right-model-right-task Opus 4.8 for architecture, Sonnet 4.8 for coding, Haiku 4.8 for classification. How to build task-based, complexity-based and cascading routing. Sun, 17 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) str: task_type = classify_task(task_description) routing_map = { "classification": "haiku-4.8", "code_generation": "sonnet-4.8", "refactoring": "sonnet-4.8", "architecture": "opus-4.8", "debugging": "sonnet-4.8", "documentation": "haiku-4.8", "security_review": "opus-4.8", } return routing_map.get(task_type, "sonnet-4.8") Strategy 2: Complexity-Based Routing Estimate complexity and route on that: def select_model_by_complexity(files_touched: int, lines_changed: int, task: str) -> str: complexity_score = ( files_touched * 10 + lines_changed * 0.1 + keyword_weight(task) ) if complexity_score > 100: return "opus-4.8" elif complexity_score > 30: return "sonnet-4.8" else: return "haiku-4.8" Strategy 3: Cascading Routing Start cheap and escalate only if you have to: def cascading_route(prompt: str) -> str: # Try Haiku first for simple tasks result = generate(prompt, model="haiku-4.8") if result.confidence < 0.8: result = generate(prompt, model="sonnet-4.8") if result.confidence < 0.8: result = generate(prompt, model="opus-4.8") return result This keeps the cost down on easy work while still landing the quality on hard work. The author's rule of thumb is that escalation adds one or two extra calls for the tasks that need it, though that is a planning heuristic rather than a measured figure. Strategy 4: Provider-Based Routing Hermes' OpenRouter integration lets you route at the provider level. The snippet below is illustrative, not a verified API, but it shows the shape of the idea: # Route based on provider strengths hermes.config.set("routing.providers", { "anthropic": { "priority": 1, "models": ["opus-4.8", "sonnet-4.8"] }, "openai": { "priority": 2, "models": ["gpt-4.1"] }, "nous": { "priority": 3, "models": ["hermes-3"] }, "z.ai": { "priority": 4, "models": ["glm-4-plus"] }, "kimi": { "priority": 5, "models": ["kimi-k2"] }, }) [OpenRouter's catalogue](https://openrouter.ai/docs/cookbook/coding-agents/hermes-integration) gives you plenty of flexibility (it listed 200+ models a while back and now carries well over 400). The hard part is choosing. Too many options just create decision paralysis. Most teams are better off starting with three to five models that cover small, medium and large task sizes. OpenHuman's Automatic Routing: [OpenHuman's single-subscription multi-model routing](https://tinyhumans.gitbook.io/openhuman/features/model-routing) is the easiest version to live with. It picks the cheapest adequate model for each task without you having to think about it. Local models handle simple classification, cloud models handle harder synthesis, and the premium models stay in reserve for jobs that genuinely warrant them. The routing logic weighs up: Task type (classification, generation, reasoning) Context size (small context goes to a smaller model) Required quality (judged on past success rates) Current provider latency and availability Cost per token OpenHuman's docs frame routing as a way to cut cost and latency. The article's "40-60% cost savings versus using a single large model" figure is presented as user-reported, but it is not independently confirmed, so read it as illustrative rather than a benchmark. Measuring Routing Effectiveness: Track these: **Cost per task**: should fall once routing is on **Quality degradation**: should stay small (the author suggests keeping any success-rate change under 5%) **Escalation rate**: share of tasks that need a bigger model (the author's target is under 20%) **Latency**: average time to completion **Savings rate**: (single-model cost minus routed cost) divided by single-model cost The escalation and quality targets above are the author's recommended heuristics, not measured results from a cited study. Multi-model routing is not really about using cheaper models. It is about using the right model for each task. The savings are what falls out of choosing well.]]> The Agent Skill Marketplace: ClawHub vs agentskills.io https://aikickstart.com.au/news/agent-skill-marketplace-clawhub-vs-agentskills https://aikickstart.com.au/news/agent-skill-marketplace-clawhub-vs-agentskills Two skill marketplaces, two philosophies: open discovery versus curated quality. Inside the sprawling ClawHub ecosystem and security-first agentskills.io. Sat, 16 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) ` and you are away Weaknesses **Security**: a [Koi Security audit found 341 malicious skills](https://www.termdock.com/en/blog/clawhub-malicious-skills-incident). A related platform flaw, CVE-2026-25253, also surfaced around the same time (more on the attack vector below). **Quality variance**: with no quality gate, reliability is all over the map **Maintenance**: abandoned skills pile up and nobody manages their lifecycle **Trust**: you cannot really know what a skill does without reading its source Post-CVE Changes This is where the original write-up gets ahead of the facts, so read it with care. ClawHub reportedly tightened things up after the incident, but the specific list of changes does not all check out against the public record. What the sources actually support is narrower: ClawHub's confirmed response, working with VirusTotal from early February 2026, was [upload-time SHA-256 scanning, daily re-scanning, and behavioural analysis](https://www.termdock.com/en/blog/clawhub-malicious-skills-incident). A publisher verification scheme arrived in March 2026, with reportedly low adoption. The original article also claimed mandatory sandboxing, cryptographic publisher signing, dynamic analysis on upload, and a paid bug bounty programme. Those are not corroborated. Sandboxing and dynamic analysis show up in security researchers' recommendations rather than as shipped features, the verification scheme is not the same thing as mandatory signing, and there is no evidence OpenClaw runs a paid bug bounty. Treat that bundle as unconfirmed. The same goes for the claim that publication time jumped from minutes to hours. No source backs it, and since the real fix was automated scanning rather than manual review, it does not square with how the system actually works. Some community members did reportedly grumble about the open marketplace getting "corporatised," but the friction story is softer than the original made out. agentskills.io: The Curated Registry: Here the original framing needs the biggest correction. It described agentskills.io as "the Hermes skill platform," a curated registry run by Nous Research that reviews every skill before publication. That is not accurate. [agentskills.io is an open standard](https://www.agensi.io/learn/agent-skills-open-standard), the SKILL.md spec, originally created by Anthropic and released openly in December 2025. Hermes skills conform to that standard; they are not the same thing as it. And Hermes itself does not manually review every skill before publishing. It runs an [automated security scanner that looks for data exfiltration, prompt injection, and malicious payloads](https://hermes-agent.nousresearch.com/docs/user-guide/features/skills). Its Skills Hub also aggregates skills across several tiers, where the Community tier is the largest, which is the opposite of a fully gated model. So read the "curated" pitch below as the direction of travel for the controlled-trust camp, not a literal description of one company's gate. Strengths **Quality**: vetted skills tend to be more reliable on average **Security**: automated scanning catches malicious or vulnerable code before it ships **Compatibility**: skills are tested against the runtime they target **Trust**: you can install with more confidence Weaknesses **Scale**: far fewer skills than ClawHub **Velocity**: any review step slows publication **Gatekeeping**: some builders feel shut out by quality bars **Centralisation**: a single platform controlling the gate makes some users wary The Hermes Approach A caveat on the code below. The original article showed a Python install API, and the fact-check could not verify it. The real Hermes interface is [CLI-based](https://hermes-agent.nousresearch.com/docs/guides/work-with-skills), along the lines of `hermes skills install openai/skills/k8s`. The snippet here, including the `verified_by`, `tested_with`, and `security_audit` metadata fields, is illustrative and reportedly does not match the shipping interface, so do not copy it expecting it to run. # Install a skill from agentskills.io hermes.skills.install("database-migration", version="^2.1.0") # Skills include metadata skill = hermes.skills.get("database-migration") print(skill.verified_by) # Reviewer identity print(skill.tested_with) # Compatible Hermes versions print(skill.security_audit) # Audit date and result Comparison: A few cells in this table carry the same caveats as the prose above. The skill counts are moving targets, the sentiment percentages have no traceable source (treat them as unconfirmed), and the install commands reflect the original article's framing rather than verified syntax for both platforms. Philosophy: Open marketplace: Curated registry Skill count: 12,847: Hundreds Security model: Review-on-report: Review-before-publish Publisher friction: Low: Medium User trust: Lower (post-CVE): Higher Community sentiment: 35% primary use: 30% primary use Malicious skills found: 341: 0 (known) Typical install: `openclaw skills install X`: `hermes.skills.install("X")` A word on that CVE. [CVE-2026-25253 is real](https://adversa.ai/blog/openclaw-security-101-vulnerabilities-hardening-2026/): a critical remote-code-execution flaw disclosed on 3 February 2026, patched in version 2026.2.12. But it was a platform vulnerability in the Control UI, which trusted a `gatewayUrl` query parameter without checking it, exploited through a malicious web page. Calling it a flaw "triggered by a malicious skill," as the original did, slightly misstates how the attack worked. The Future: Hybrid Models: The open-versus-curated argument is old news. [npm, PyPI, and crates.io all started open and bolted on security and verification later](https://hermes-agent.nousresearch.com/docs/user-guide/features/skills). The author's bet, and it is a bet rather than a settled fact, is that agent skills land on a tiered middle ground: **Unverified tier**: anyone can publish, everything runs in a heavy sandbox **Community verified**: skills that clear endorsement and usage thresholds **Officially verified**: skills audited by the platform team and fully trusted The appeal is choice. You take speed and breadth in the unverified tier, balance in the community tier, and safety in the official one. There is some real support for the direction: Hermes already runs tiered trust levels (built-in, official, trusted, and community). ClawHub's post-incident scanning and verification push points the same way. The fully fleshed-out three-tier model, though, is a forecast, not something any platform has shipped end to end. Building Skills: Best Practices: Whether you publish to ClawHub, to a Hermes-style registry, or anywhere else: **Document thoroughly**: include examples, constraints, and failure modes **Test comprehensively**: unit tests, integration tests, and edge cases **Version carefully**: use semantic versioning and spell out breaking changes **Secure obsessively**: no eval, no shell execution, no undocumented network calls **Handle errors gracefully**: fail with a clear message, not a cryptic stack trace **Respect constraints**: accept and enforce whatever limits the user sets **Minimise dependencies**: every dependency is another link in your supply chain Here is the part worth sitting with. Models are converging, and the gap between the top systems keeps narrowing. Skills are doing the opposite: multiplying, specialising, and turning into the real point of difference. The platform that ends up with the skills people actually trust, broad enough to be useful and safe enough to install without a second thought, is the one that wins the users. The Koi Security audit was a reminder of what happens when trust is an afterthought.]]> Building Voice-Enabled Coding Agents https://aikickstart.com.au/news/building-voice-enabled-coding-agents https://aikickstart.com.au/news/building-voice-enabled-coding-agents OpenHuman's on-device STT/TTS makes voice-driven development practical. The architecture, workflows, limits, and adding voice to Hermes and Claude Code. Fri, 15 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Speech-to-Text -> Agent Processing -> Text-to-Speech -> Voice Output Speech-to-Text (STT) OpenHuman uses Whisper for speech recognition and runs it locally on the [Tauri](https://tinyhumans.gitbook.io/openhuman/features/native-tools/voice) v2 runtime. (The project documents Whisper-based STT and a Tauri build; the framing of a model "derived" from Whisper and tuned for Tauri specifically goes a bit beyond what the docs actually say.) Running on-device means: No audio leaves your machine It works offline Latency is reportedly around 200-500ms for a 10-second utterance, though that figure is not published by OpenHuman and looks like an estimate It is said to support English, Mandarin, Spanish, and Japanese, though the docs do not list supported languages The agent is also described as recognising technical vocabulary (function names, library names, coding terms) more reliably than generic Whisper. That claim is unconfirmed; the docs mention punctuation and dictation cleanup, not a coding-specific fine-tune. Agent Processing The transcribed text goes into the agent's normal pipeline. OpenHuman treats a spoken command the same as a typed one. "Create a new function called calculate total that takes an array of prices" runs the same way whether you say it or type it. Text-to-Speech (TTS) Responses are read back using a lightweight TTS model. OpenHuman ships [Piper for local voice and ElevenLabs for cloud voice](https://tinyhumans.gitbook.io/openhuman/features/native-tools/voice), and you can pick the voice you want. Some developers reportedly bump the speech rate to 1.5x for routine confirmations and drop back to 1.0x for longer explanations, though an adjustable rate is not something OpenHuman documents. Practical Voice Workflows: Workflow 1: Hands-Free Code Review Review code while you eat lunch or walk around: You: "Read the auth middleware file" Agent: "Reading auth middleware. The file has 47 lines. It validates JWT tokens..." You: "What exceptions does it handle?" Agent: "It handles TokenExpiredError, InvalidTokenError, and MissingTokenError." You: "Add handling for MalformedTokenError" Agent: "Added MalformedTokenError handling. Should I also add a test for it?" You: "Yes, add a test" Workflow 2: Rapid Note Capture Grab an idea without breaking your flow: You: "Note: the database migration needs a rollback script" Agent: "Noted. I will add it to the migration task in your Memory Tree." Those notes land in OpenHuman's [Memory Tree](https://tinyhumans.gitbook.io/openhuman), a hierarchical store of Markdown files backed by a local SQLite database. Workflow 3: Meeting Participation OpenHuman can [join a Google Meet call as a real participant](https://tinyhumans.gitbook.io/openhuman/features/mascot): it hears everyone, takes notes, can speak back, and pipes its animated face in as the camera feed. You: "Join the standup and take notes" Agent: "Joining the standup. I will transcribe and extract action items." After the meeting: You: "What were my action items?" Agent: "Three action items: fix the login bug, review Sarah's PR, and update the API documentation." Limitations (June 2026): Voice is not yet a primary way to write code. The sticking points: **Precision**: Code is exact; speech is loose. "Function called calculate total that takes an array of numbers" is clear. "The thing that does the sum with the list" is not. **Context**: Voice has none of the visual context of an IDE. You cannot point at a line while you talk. **Environment**: Open offices and background noise drag accuracy down fast. **Privacy**: Saying a coding task out loud tells everyone near you what you are working on. **Complexity**: Multi-step reasoning is harder to track by ear than by eye. When Voice Works Best: Voice coding earns its keep for: **Quick queries**: "What does this function do?" **Note capture**: "Remind me to fix the auth bug" **Simple commands**: "Run the tests" **Documentation**: dictating comments and docstrings **Accessibility**: developers with repetitive strain injury or visual impairments It falls down on: **Complex refactoring**: too many files, too many constraints **Precise syntax**: "Angle bracket question mark extends T greater than" is worse than typing `` **Visual review**: reading diffs and comparing screenshots Implementation for Other Agents: [Hermes](https://hermes-agent.org/) and Claude Code do not ship a native voice interface, but you can bolt one on. (Hermes Agent from Nous Research lists multi-channel access over Telegram, Slack, Discord and the terminal, with no documented voice mode; Claude Code is a CLI with no built-in voice either.) # Voice bridge for Hermes import speech_recognition as sr def voice_command(): recognizer = sr.Recognizer() with sr.Microphone() as source: audio = recognizer.listen(source) text = recognizer.recognize_whisper(audio) return hermes.execute(text) That pattern uses the [Uberi/SpeechRecognition](https://github.com/Uberi/speech_recognition) Python library, whose `Recognizer`, `Microphone`, `listen()` and `recognize_whisper()` calls all work as shown. For Claude Code, macOS has built-in system dictation that types into any text field, including a terminal. Some people pair it with third-party STT tools (one reportedly named WhisperDesktop, which I could not verify as a current product) to feed the terminal. Voice is the easiest way to interact with a coding agent casually. It will not take over from typing for precise work. For most of the quick stuff around that work, it is on track to become the default.]]> Real-Time Agent Monitoring: Logs, Traces, Observability https://aikickstart.com.au/news/real-time-agent-monitoring-observability https://aikickstart.com.au/news/real-time-agent-monitoring-observability The three-pillar monitoring stack for production agents: structured logging, distributed tracing and aggregate metrics, plus debugging workflows. Thu, 14 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) 50% Success rate: Gauge: <80% Average latency: Histogram: p95 >60s Token cost per task: Histogram: >200% of baseline Rollback rate: Gauge: >5% Approval gate triggers: Counter: Spike >300% Tool error rate: Gauge: >2% per tool Monitoring Stack Recommendations: For Small Teams (< 10 engineers) Hermes: Built-in FTS5 logs + `hermes metrics` command Claude Code: Built-in telemetry + JSON log export OpenClaw: File logs + basic metrics dashboard Export to: Grafana Cloud (free tier) or Datadog A note on those Hermes and OpenClaw commands: the specific subcommands shown here are illustrative. Hermes ships a CLI, but the trace, metrics, and dashboard verbs below were not confirmed in its primary docs, and the OpenClaw commands could not be verified at all. Claude Code's telemetry, by contrast, is documented, and its OpenTelemetry export feeds Grafana, Datadog, and similar backends directly ([Claude Code Docs, 2026](https://code.claude.com/docs/en/agent-sdk/observability)). For Large Teams (10+ engineers) Hermes: OpenTelemetry export to Jaeger + Prometheus Claude Code: Anthropic-managed telemetry + SIEM integration OpenClaw: Structured logging to ELK/Loki stack Dashboards: Grafana with custom agent dashboards Alerting: PagerDuty/Opsgenie for critical thresholds The SIEM piece is worth flagging because it is real and useful: Claude Code's `tool_decision`, `tool_result`, `mcp_server_connection`, and `permission_mode_changed` events form a per-user audit trail you can forward to a security information and event management platform ([Claude Code Docs, 2026](https://code.claude.com/docs/en/agent-sdk/observability)). Grafana, Jaeger, Prometheus, ELK, Loki, PagerDuty, and Opsgenie are all standard tools, and OpenTelemetry's OTLP export plugs into them, so this stack is technically sound rather than aspirational. Real-Time Dashboards: A useful agent dashboard surfaces: **Current activity**: Active agents, running tasks, queued requests. **Health overview**: Success rates, error rates, latency percentiles. **Cost tracking**: Spend today, this week, this month, broken down per agent. **Quality trends**: Rollback rate, human correction rate, approval gate stats. **Alert feed**: Active alerts and recent resolutions. # Hermes built-in dashboard hermes dashboard --port 8080 # Claude Code telemetry export claude telemetry export --format prometheus # OpenClaw metrics openclaw metrics --serve --port 9090 One caveat on the Claude Code line: there is no documented `claude telemetry export --format prometheus` subcommand. In practice you configure the export through OpenTelemetry environment variables (`OTEL_METRICS_EXPORTER` and the standard OTLP settings), and a Prometheus or Grafana backend consumes the metrics from there ([Claude Code Docs, 2026](https://code.claude.com/docs/en/agent-sdk/observability)). Read the command above as shorthand for "point your OTEL config at Prometheus." Alerting Best Practices: **Alert on symptoms, not causes**: "Success rate dropped," not "CPU usage high." **Use dynamic thresholds**: Static thresholds breed alert fatigue. Lean on anomaly detection. **Include context**: An alert should link straight to the relevant traces and logs. **Escalation paths**: Low-priority alerts to Slack, high-priority to PagerDuty. **Review regularly**: A weekly alert review to clear out false positives. Debugging with Traces: When an agent does something you did not expect, the trace is the first place to look: # Find the failing trace hermes traces list --since 1h --status failed # Inspect the trace hermes traces show trace_abc123 --format tree # Compare with a successful trace hermes traces compare trace_abc123 trace_def456 The comparison shows where two runs diverged: a different tool choice, different context, a different model response. That is usually enough to pin down the root cause. (As above, the exact `hermes traces` verbs are illustrative and not confirmed in the project's primary docs, but the workflow holds for any tracing tool you adopt.) Monitoring is not optional for production agents. An agent you cannot see is a risk on your books. An agent you can see, with logs, traces, and metrics behind it, is an accountable member of the team.]]> Agent Deployment Patterns: From Laptop to Production https://aikickstart.com.au/news/agent-deployment-patterns-laptop-to-production https://aikickstart.com.au/news/agent-deployment-patterns-laptop-to-production Six proven deployment patterns for agentic systems, from local-first to multi-region orchestrated, plus the checklist every production agent must pass. Wed, 13 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) [Cloud Gateway] <-- --> [OpenRouter] **Best for**: privacy-sensitive organisations that still need team features. **Pros**: local data stays local, the cloud handles scale, you get some of each. **Cons**: a more complicated architecture, latency on the cloud calls, and a security model split across two places. Deployment Checklist: Before you put any agent into production: Sandboxing configured (container or VM-based) Approval gates enabled for high-risk operations Secrets management (no API keys sitting in environment variables) Logging and monitoring configured Backup and recovery tested Rollback procedure documented Rate limiting enabled Health check endpoint configured TLS/SSL for all external communication Access controls (who is allowed to invoke the agent) Cost alerts and budgets set Documentation for whoever operates it CI/CD for Agents: Agents deserve their own CI/CD pipelines, same as any other service you ship. # .github/workflows/agent-ci.yml name: Agent CI on: [push] jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Test agent skills run: hermes skills test --all - name: Validate harness run: omnigent validate - name: Integration tests run: pytest tests/integration/ That `omnigent validate` step leans on [Omnigent](https://github.com/omnigent-ai/omnigent), the agent framework Databricks open-sourced in June 2026, which treats validation and test flows as first-class workflow artifacts. The exact `omnigent validate` and `hermes skills test --all` subcommands match how the tools work but were not confirmed word for word in the docs, so check before you copy. Deploying an agent is not a single step. It is a loop: develop, test, deploy, monitor, update, repeat. The patterns above give you the infrastructure. The discipline you bring to that loop is what decides whether the thing stays up.]]> The 10 Bets That Define Elite Agentic Coding in 2026 https://aikickstart.com.au/news/ten-bets-elite-agentic-coding-2026 https://aikickstart.com.au/news/ten-bets-elite-agentic-coding-2026 Ten strategic bets defining elite agentic coding in 2026, from agents over assistants to harness engineering over hands-on direct coding. Tue, 12 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Custom Agents in 50 Lines of Code https://aikickstart.com.au/news/custom-agents-50-lines-of-code https://aikickstart.com.au/news/custom-agents-50-lines-of-code You do not need a framework to build a useful agent. A minimal agent needs only a loop, a model, tools, and memory. Here is how to build one from scratch. Mon, 11 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Agent Failure Modes: What Goes Wrong and How to Fix It https://aikickstart.com.au/news/agent-failure-modes-what-goes-wrong https://aikickstart.com.au/news/agent-failure-modes-what-goes-wrong Agents fail in predictable ways. Understanding the taxonomy of failure modes lets you build harnesses that prevent them. Sun, 10 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) The Psychology of Trust: How Much Do You Trust Your Agents? https://aikickstart.com.au/news/psychology-of-trust-how-much-trust-agents https://aikickstart.com.au/news/psychology-of-trust-how-much-trust-agents Trust in AI agents is not binary. It is a calibrated spectrum that grows with experience, and understanding it helps teams deploy agents faster and safer. Sat, 09 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) End-to-End Autonomous Agents: From Prompt to Production https://aikickstart.com.au/news/end-to-end-autonomous-agents-prompt-to-production https://aikickstart.com.au/news/end-to-end-autonomous-agents-prompt-to-production The holy grail of agentic coding: an agent that takes a prompt, plans, writes the code, runs the tests and deploys. How close are we in June 2026? Fri, 08 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) [Plan Mode] -> [Sub-agent Execution] -> [Verification] -> [Approval Gate] -> [Deploy] Claude Code's [Dynamic Workflows](https://claude.com/blog/introducing-dynamic-workflows-in-claude-code) running on [Opus 4.8](https://www.anthropic.com/news/claude-opus-4-8) can handle the first four stages for well-scoped work. Give it a prompt like 'Add a billing history endpoint that returns paginated invoices with filters for date range and status', and the agent can: **Plan**: Break the job into schema design, route implementation, controller logic, repository queries, tests, and documentation. Name the dependencies and the risks. **Execute**: Spin up specialist sub-agents for each piece. The API agent designs the endpoint. The database agent writes migrations. The test agent generates coverage. **Verify**: Run compilation, linting, type checking, and the full test suite. Security scan with `npm audit`. Check for breaking changes. **Gate**: Hand you a summary: 8 files changed, 4 tests added, 0 breaking changes, estimated review time 5 minutes. Then wait for a human to approve. **Deploy**: Once approved, create a branch, commit in conventional commit format, push, and open a pull request. Teams with enough trust auto-merge when every check passes. By the author's own estimate, this pipeline handles roughly 60-70% of routine feature work on established codebases. That is not a benchmark figure, but it is genuinely useful in practice. What We Cannot Do Yet: The other 30-40%, on the author's reckoning, still leans on human judgment that agents cannot stand in for: **Architectural decisions**: 'Should we use a message queue or a direct API call?' turns on taste, team context, and non-functional requirements that an agent cannot fully model. **Novel problems**: Agents are strong on patterns they have seen before. Genuinely new problems call for creative thinking that current models tend to fumble. **Cross-system coordination**: Changes that span several services, teams, or organisations need negotiation and sign-off. An agent cannot run those conversations. **Production incidents**: Under time pressure, with symptoms that do not point anywhere clean, a human reads the situation better than agentic reasoning does. Let an agent assist on incidents, but do not let it lead. **Stakeholder communication**: Explaining trade-offs to a product manager, winning buy-in for a breaking change, managing expectations. That work is human at the core. The Trust Gradient: Autonomy is a slider, not a switch: L0: Assisted: Agent suggests, human decides: Fully available ([Copilot](https://github.com/features/copilot)) L1: Delegated: Agent executes routine tasks, human verifies: Production-ready ([Claude Code Task System](https://code.claude.com/docs/en/sub-agents)) L2: Supervised: Agent works independently, human monitors: Available for scoped tasks ([Hermes learning loop](https://github.com/NousResearch/hermes-agent)) L3: Autonomous: Agent plans, executes, and deploys; human reviews exceptions: Experimental L4: Fully autonomous: No human in the loop: Reportedly out of reach with current models Most teams belong at L1-L2. L3 asks for high trust, a mature harness, and a tightly scoped problem domain. Building Toward L3 Autonomy: Teams pushing for more autonomy should put their money into: **Harness maturity**: The failure-resistant harness from article 37, with every gate and constraint in place. **Verification pipelines**: Testing thorough enough that human review becomes a formality rather than a safety net. **Rollback infrastructure**: One-command rollback, feature flags, and blue-green deployments. **Monitoring**: Real-time alerting on agent-deployed changes, with anomaly detection that fires on its own. **Gradual expansion**: Start with documentation and tests. Move to isolated features. Then shared utilities. Core business logic comes last. **Human review sampling**: At L3, humans check a sample of agent changes instead of every one. The sample rate follows the quality you actually measure. The Safety Ceiling: The thing holding back full autonomy is not model capability. It is safety. An agent that is 99% correct will break production 1% of the time. For most organisations, that is not a risk worth running. The fix is not smarter models, though those help. It is better harnesses. The argument goes like this: a robust enough harness, with sandboxing, verification gates, rollback, and monitoring, could in principle make a 99% correct agent safer than a 99.9% correct human, because the agent never skips the harness. That is a claim about design, not a measured result, but it points at where the work needs to go. End-to-end autonomy is on its way. The author's bet is that it arrives through better harnesses rather than better models. The teams putting safety infrastructure in place now are the ones most likely to use that autonomy first.]]> The Agentic Engineer: New Role or Same Job, Better Tools? https://aikickstart.com.au/news/the-agentic-engineer-new-role-or-better-tools https://aikickstart.com.au/news/the-agentic-engineer-new-role-or-better-tools Agentic coding changes what engineers do, but does it change who they are? The case for a new role with new skills, new metrics and a new bond with code. Thu, 07 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Agentic Coding 2.0: Agents Conducting Other Agents https://aikickstart.com.au/news/agentic-coding-2-agents-conducting-agents https://aikickstart.com.au/news/agentic-coding-2-agents-conducting-agents Agentic coding 2.0 puts a lead agent in charge of specialists, separating what has shipped from the hype for Australian engineering teams. Sat, 30 May 2026 00:00:00 GMT Code daniel.fleuren@aikickstart.com.au (Daniel Fleuren) How to get your business cited in ChatGPT and Claude https://aikickstart.com.au/news/how-to-get-cited-chatgpt-claude https://aikickstart.com.au/news/how-to-get-cited-chatgpt-claude A practical GEO guide for becoming easier for AI answer engines to understand, compare, and cite when customers ask for recommendations. Tue, 16 Jun 2026 00:00:00 GMT SEO/GEO daniel.fleuren@aikickstart.com.au (Daniel Fleuren) GEO vs SEO: what's the difference and why you need both https://aikickstart.com.au/news/geo-vs-seo-whats-the-difference https://aikickstart.com.au/news/geo-vs-seo-whats-the-difference A clear comparison of generative engine optimisation and search engine optimisation across discovery, ranking signals, content format, and measurement. Mon, 15 Jun 2026 00:00:00 GMT SEO/GEO daniel.fleuren@aikickstart.com.au (Daniel Fleuren) What is GEO optimisation? The complete guide for Australian businesses https://aikickstart.com.au/news/what-is-geo-optimization-complete-guide https://aikickstart.com.au/news/what-is-geo-optimization-complete-guide A practical guide to generative engine optimisation: how AI engines cite sources, which content formats get quoted, how to build entity authority, and how to measure it. Mon, 15 Jun 2026 00:00:00 GMT SEO/GEO daniel.fleuren@aikickstart.com.au (Daniel Fleuren) n8n vs Make vs Zapier: which automation platform should you choose? https://aikickstart.com.au/news/n8n-vs-make-vs-zapier https://aikickstart.com.au/news/n8n-vs-make-vs-zapier An honest comparison of n8n, Make, and Zapier across data sovereignty, cost at scale, self-hosting, AI and agent support, and learning curve. Mon, 15 Jun 2026 00:00:00 GMT Automation daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Multi-agent orchestration explained for business leaders https://aikickstart.com.au/news/multi-agent-orchestration-explained https://aikickstart.com.au/news/multi-agent-orchestration-explained A plain-English explainer on multi-agent orchestration: what it is, the research-decide-act pattern, human approval gates, and when to use a single agent instead. Mon, 15 Jun 2026 00:00:00 GMT AI Agents daniel.fleuren@aikickstart.com.au (Daniel Fleuren) How to deploy local AI on a VPS: a practical guide https://aikickstart.com.au/news/how-to-deploy-local-ai-on-a-vps https://aikickstart.com.au/news/how-to-deploy-local-ai-on-a-vps A step-by-step guide to running AI on your own Australian VPS, covering data sensitivity assessment, model choice, PII redaction with Microsoft Presidio, and approval gates. Mon, 15 Jun 2026 00:00:00 GMT Secure AI daniel.fleuren@aikickstart.com.au (Daniel Fleuren) 7 AI automation workflows that save teams 10+ hours a week https://aikickstart.com.au/news/7-ai-automation-workflows-that-save-hours https://aikickstart.com.au/news/7-ai-automation-workflows-that-save-hours Seven proven AI automation workflows, each with the job it replaces, how it is built, the time it saves, and the guardrail that keeps it safe. Mon, 15 Jun 2026 00:00:00 GMT Automation daniel.fleuren@aikickstart.com.au (Daniel Fleuren) AI automation for small business: a 2026 Australian guide https://aikickstart.com.au/news/ai-automation-for-small-business-australia https://aikickstart.com.au/news/ai-automation-for-small-business-australia A practical, cost-aware guide to AI automation for Australian small businesses in 2026, with AUD cost ranges, realistic ROI timeframes, and a safe starting point. Mon, 15 Jun 2026 00:00:00 GMT Automation daniel.fleuren@aikickstart.com.au (Daniel Fleuren) How to build an AI roadmap for your business https://aikickstart.com.au/news/how-to-build-an-ai-roadmap-for-your-business https://aikickstart.com.au/news/how-to-build-an-ai-roadmap-for-your-business A practical guide to prioritising AI opportunities, choosing the first workflow, and turning AI ideas into a delivery roadmap. Wed, 03 Jun 2026 00:00:00 GMT AI Strategy daniel.fleuren@aikickstart.com.au (Daniel Fleuren) The best AI tools for startups in 2026 https://aikickstart.com.au/news/best-ai-tools-for-startups-in-2026 https://aikickstart.com.au/news/best-ai-tools-for-startups-in-2026 A founder-friendly way to compare AI tools without buying a stack that nobody uses. Wed, 03 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) How AI automation saves teams hours every week https://aikickstart.com.au/news/how-ai-automation-saves-teams-hours-every-week https://aikickstart.com.au/news/how-ai-automation-saves-teams-hours-every-week Where AI automation actually saves time, and how to keep approvals, logs, and quality controls in place. Wed, 03 Jun 2026 00:00:00 GMT Automation daniel.fleuren@aikickstart.com.au (Daniel Fleuren) AI agents explained for business owners https://aikickstart.com.au/news/ai-agents-explained-for-business-owners https://aikickstart.com.au/news/ai-agents-explained-for-business-owners A plain-English explanation of AI agents, what they can do, and how to deploy them safely. Wed, 03 Jun 2026 00:00:00 GMT Agents daniel.fleuren@aikickstart.com.au (Daniel Fleuren) How to choose the right AI tools without wasting money https://aikickstart.com.au/news/how-to-choose-the-right-ai-tools-without-wasting-money https://aikickstart.com.au/news/how-to-choose-the-right-ai-tools-without-wasting-money A simple selection framework for choosing AI tools by value, risk, adoption, and workflow fit. Wed, 03 Jun 2026 00:00:00 GMT AI Tools daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Secure document AI without leaking sensitive files https://aikickstart.com.au/news/secure-document-ai-without-leaking-sensitive-files https://aikickstart.com.au/news/secure-document-ai-without-leaking-sensitive-files How to design practical document AI workflows with redaction, scoped access, audit trails, and human review. Wed, 03 Jun 2026 00:00:00 GMT Secure AI daniel.fleuren@aikickstart.com.au (Daniel Fleuren) Open design agent systems for business teams https://aikickstart.com.au/news/open-design-agent-systems-for-business-teams https://aikickstart.com.au/news/open-design-agent-systems-for-business-teams How reusable agent design systems help teams document prompts, components, tokens, governance, and delivery patterns. Wed, 03 Jun 2026 00:00:00 GMT Agent Systems daniel.fleuren@aikickstart.com.au (Daniel Fleuren) SEO/GEO lessons from local service growth https://aikickstart.com.au/news/seo-geo-lessons-from-local-service-growth https://aikickstart.com.au/news/seo-geo-lessons-from-local-service-growth What local service businesses can learn from Mufflermen-style SEO/GEO content systems and generative answer visibility. Wed, 03 Jun 2026 00:00:00 GMT SEO/GEO daniel.fleuren@aikickstart.com.au (Daniel Fleuren)