Max Nardit
Data & AI Systems Engineer working on visibility, measurement, and agentic systems.
AI now sits between people and what they’re looking for, and between work and the software that runs it. It answers, routes, remembers, forgets, and now acts on its own. Usually before anyone can check whether it got things right. I study that layer with original data and build the tools to work inside it. My background is the supply side of digital marketing: the crawl, the analytics, the automation and reporting, the plumbing under what looked like marketing. The marketing was never really the problem. Visibility, measurement, and control were. AI didn’t make that problem smaller. It moved it somewhere you can’t see.
Beetroot featured in 窓の杜 (Japan) · original-data research · shipped open-source tools
the systems that decidewhat gets found, trusted,and acted on
01 / Thesis
Operating thesis
AI is changing two things at once: how people find information, and how work moves through software.
That shift isn’t only a search problem. It touches tracking, attribution, context, memory, handoff, and trust: the systems that decide what a person sees before they make a choice.
I work on that layer. Some of it is research: measuring what changes and publishing what holds up. Some of it is engineering: building tools and workflows that keep context, expose failures, and make AI-assisted work inspectable.
02 / Focus
Current areas
- 01
Visibility & discovery
How people, businesses, and tools stay findable when AI systems answer, summarize, route, and act.
- 02
Measurement & tracking
How to know what’s working when clicks, cookies, referrals, and dashboards stop telling the whole story.
- 03
Agentic systems
Memory, handoff, orchestration, tool boundaries, and recovery for agents that touch real workflows.
- 04
Operational evidence
Original-data research, field notes, and shipped tools. Findings over forecasts.
03 / Artifacts
Selected artifacts
Tools I’ve built around the same layer: memory, clipboard, agent handoff, monitoring. Local-first where it makes sense, from problems I hit directly.
- 01BeetrootA local-first clipboard environment for preserving workflow context on Windows.
- 02Clipboard MCPA clipboard bridge between humans and AI agents.
- 03Share2AgentA browser-to-agent handoff surface.
- 04Agent RecallScoped persistent memory for long-running coding agents.
- 05Claude Usage DeckA small operational monitor for Claude.ai limits.
04 / Writing
Recent writing
All articles →Agentic workflows: one word for two opposite designs, and the difference is who owns the loop
Anthropic's taxonomy and GitHub's product disagree on what the term covers, so the label settles nothing about a design. One test does: hand an LLM the steering only when an outside check, not its own claim, can confirm the job is finished.
Anthropic's always-on agents guide: what the inbox, timers and outbox do when a worker dies, tested in SQLite
Most of the failure handling the guide leaves out comes down to one move: make every wake-up an inbox event with a key the database refuses to store twice. Retried webhooks, timer replays, approval answers and their expiries all fit through that one constraint. Leases, retries and the outbox need a little more.
Claude Code subagents: when they are worth it, job by job, and when the main session is cheaper
Delegation is billed in tokens and in trust: the subagent pays to read the mess, and the parent gets a paraphrase instead of the raw output. Test runs, codebase search, code review, parallel research and parallel edits each get a verdict, with the list-price break-even behind it and the one case where the arithmetic says stay and you should delegate anyway.
How to build an MCP server in 2026: one TypeScript factory, both protocol eras, and what the SDK's HTTP handler leaves to you
One factory serves both transports and both generations of clients. In a test run the SDK handler answered a forged Origin with 200 and gave clients no freshness window to cache by, and the Inspector checked only the old handshake until asked for the new one. The two guards to add, the cache hints to set, and what a first server can leave out.
Claude Code Code Mode: auto mode now reviews the script, not each tool call
In a Code Mode session the auto mode classifier reads the script once and never the calls inside it, so a path or host computed at run time gets no review from it. A PreToolUse hook that can't start or times out now refuses the call, but one that exits 1 still lets it through. The checks that see real values are your rules, your hooks and the sandbox.
Self-hosted Claude Managed Agents: the server is yours, and so are the failures that report nothing
Self-hosting moves custody of the transcripts to you, and the operations come with it. Anthropic's list of differences names the cases where your server says success, or nothing, while the work is stuck, dropped or answered by another model. Those rows are the acceptance test for a deployment.
05 / Contact
Get in touch
Email or Telegram both reach me. Telegram is faster.