TAG
#Agent
2026-10 4 posts
-
In the Agent Era, the Scope a Specialist Software Supplier Can Choose
Part 4 of 4: lock agent features in one dedicated agent, or expose them as tools and work assets any worker can use? It shapes what a supplier can sell.
-
Seeds and Germination: Software That Evolves in the Field
Part 3 of 4: fitting a product to each customer site with people and agents, building runtime adaptation into it, and feeding field experience back.
-
Every Organization Needs an Agent Runtime
Part 2 of 4: why even air-gapped organizations will run a general-purpose agent runtime on work PCs, and how to connect it to internal models and tools.
-
Separating the Worker from the Tool
Part 1 of 4: work spans products, so general-purpose agents become workers and products their tools. What to expose, and where software keeps its value.
2026-09 2 posts
-
Can tgrep, CodeGraph, Mantic, or ripwire Replace ripgrep?
tgrep, CodeGraph, Mantic, and ripwire vs ripgrep on eight repos. Each hinges on a different variable: query, language coverage, file names, or phrasing.
-
ego-browser and Aside Fail Differently
Same missions, two browser agents: ego-browser isolates its tabs and returned success on missed clicks; Aside works in your real tabs and threw errors.
2026-05 5 posts
-
Requirements as Latent State
A requirement is a latent state and the user's sentence a noisy observation. What follows for EARS, spec-driven development, harnesses, and when to ask.
-
Skill and Harness
A skill compresses how to behave; a harness organizes how to tell if that behavior nears the goal. Why the two still contain each other in practice.
-
Harness as Environment
A vector DB full of experience does not make an agent adapt. That takes a harness: what may change, how success is judged, how far a failure rolls back.
-
Memory as Adaptation
Long-running agents need more than a RAG store: why memory split into working, episodic, semantic, and procedural layers that ground policy adaptation.
-
Weights, Prompts, Codes as Parameters
If agent problems are POMDPs, weights, prompts, and code are parameters at three layers of one policy space. Why the layers opened in that order.
No matching posts.