When I built clive, the core insight was deceptively simple: don't give the agent a list of tools. Give it an environment.An API is a call-response primitive. You invoke it, it returns something, the state lives somewhere else. An environment is a thing you inhabit. You enter it, act inside it, leave it different than...
Author: Martin Treiber
The Cost Sheet Problem Nobody Talks About
A cost sheet is more than a budget document. It is the financial blueprint of an engagement — capturing manpower rates, vendor costs, planned invoices, outgoing payments, and deliverables, all in one place. It's the heart of the project. When it's accurate and up to date, it tells you whether the project is financially healthy....
Clive Can Now Modify Itself
We've been building clive — a CLI Live Environment that gives an LLM a terminal and a keyboard. The core idea is simple: instead of wrapping tools in APIs and schemas, you let the agent read the screen and type. The terminal becomes the interface. The loop becomes the protocol. We've added something that takes...
The Terminal as Agent Interface: Introducing clive
There is a quiet assumption embedded in most agent infrastructure: that agents need structured interfaces. APIs, schemas, tool definitions, protocols like MCP or A2A. The assumption is that the gap between an LLM and a system needs to be bridged by something machine-readable. clive starts from a different assumption. LLMs are excellent at reading text...
The Case for a Single Source of Truth: Why Integrated PMO Tools are Non-Negotiable
In many organizations, "Project Management" is synonymous with "Data Hunting.". When a PMO (Project Management Office) doesn't have a centralized tool, they don't actually manage projects — they manage spreadsheets. According to Wellingtone's 2025 State of Project Management report, 42% of PMOs still spend at least one full working day every month doing nothing but...
Departments Are Albums: Agentic AI and the Coming Corporate Unbundling
In 2000, the music industry had a problem it misdiagnosed. Napster was stealing albums. The fix was obvious: stop the theft, protect the bundle. The album — twelve songs, a cover, a price — had structured the industry for fifty years. Labels, distributors, retailers, and artists all organized themselves around it. By 2003, iTunes had...
Code as Action: The Pattern Behind Programmatic Tool Calling
There's a design decision buried inside every AI agent that most developers make without realizing they've made it: what is the atomic unit of action? For most agent systems built in the last two years, the answer is a tool call — a single function invoked with a JSON payload, its result surfaced back to...
A Practical Guide to Getting Started with OpenClaw
Somewhere in early February, Andrej Karpathy — founding member of OpenAI, former AI director at Tesla, a person not easily impressed by internet phenomena — logged onto a Reddit-like site for AI bots and described what he was reading as "genuinely the most incredible sci-fi takeoff-adjacent thing I have seen recently." The site was Moltbook....
Your Agent Framework Is a Monolith. The Browser Doesn’t Care.
Last week, I dropped an LLM agent into a plain HTML file. No Node.js. No Webpack. No Docker container running a Python backend that proxies to another Python backend. One <script type="module"> tag, a couple of imports, and an agent that reasons, calls tools, writes code, and delegates to sub-agents — all orchestrated entirely client-side,...
Vercel’s Eval Data Suggests Static Context Beats Skill Retrieval for AI Coding Agents
There's a recurring theme in AI engineering that never gets old: the "dumb" approach beating the sophisticated one. This time, Vercel has the receipts. The company published eval results on January 27, 2026, comparing two approaches for teaching AI coding agents about Next.js 16 APIs — framework features like use cache, connection(), and forbidden() that...
