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 RAG vs agentic search: why coding agents dropped the vector index, and where retrieval still wins
Claude Code started on a vector database and moved to grep. Cursor measured a gain from embeddings, then built an exact index for regex and removed semantic search from its SDK. What an agent needs from its search tools is an empty result it can act on, and exact search can be built to give one.
Claude Code GitHub Actions: set up @claude in your repo without handing a PR author your secrets
The install is one command, and the action's defaults do more than the workflow file shows. Three of its controls still stop less than their names suggest: the write-access check, the permissions block and the command restriction on outside pull requests.
Claude Code vs GitHub Copilot: seven ways developers split the work, and how much of your Claude Code setup each Copilot surface reads
Copilot runs Claude models at Anthropic's list rates, reads CLAUDE.md and the skills folder, and its CLI even loads Claude Code hooks. So the split is no longer one vendor against the other. It runs surface by surface: each Copilot surface reads a different slice of your Claude Code setup, and the slice decides which rules reach the code.
Codex sandbox permission profiles vs the Claude Code sandbox: what each one walls off
On Ubuntu, a Codex profile with a one-host allowlist refused an unlisted site with a 403. Delete two lines that look like an unrelated feature switch and the same site answers 200, with no warning. Claude Code's network filter cannot go inert that way; it is off until you turn it on, and one permission mode walks through it.
Gemini 4 Neon on SWE-sweep: 39.0% in the Antigravity CLI, 12.8% in mini-SWE-agent, and Google ran both rivals' agents itself
In the same minimal harness Neon is a point ahead of GPT-6.2 Sol; in each vendor's own agent, thirty. Most of that swing is one cell, Sol in Codex, which Google ran itself and which scores below Sol in the minimal harness.
Claude linked billing: billing_policy lets the customer pay, but the request still runs under your organization
One misread 403 can move all tenants onto your bill, while a wrong header charges somebody else. Where those failures hide, and what to log first.
05 / Contact
Get in touch
Email or Telegram both reach me. Telegram is faster.