Anton Dziatkovskii

Anton Dziatkovskii

I run a coding-agent fleet of six vendors on five machines, and I talk about what breaks, with the logs on screen.

My agents once spent a night filing 126 incidents about a network that was fine. The Mac was asleep. On stage I tell stories like that one and keep the incident reports and the power log on screen.

Invite me to speak (15-min call) Email Sessionize profile GitHub

Numbers you can check

48 merged PRsin 33 other people's repos since 1 Aug 2026: 37 code and docs fixes plus 11 curated-list entries. Includes UK AISI inspect_ai, Qwen Code, the MCP Go SDK, Pydantic Logfire and the Gemini cookbook. Full list
6 agent tools · 5 machinesClaude Code, Codex, Grok, Gemini, GLM and Mistral daily on one shared fleet, with a written rulebook, a shared skill shelf and an incident journal
58 eventsI hosted in 2025, mostly the weekly Collective Call (Luma calendar of the Palo Alto AI Research Lab). Largest page: 245 registrations
8.99K · 445subscribers and videos on the YouTube channel @AAACRM
Since 2015hired COO/CTO, leading a distributed team of 40+ developers. Programmer: Python and C++
MSc · PhDMSc in computer security (MEPhI), PhD. Nine 2026 preprints with DOIs, h-index 7 on Google Scholar

Pull-request and YouTube counts re-measured on 3 Oct 2026. Nothing here is rounded up.

Talks

Stage 20-30 minLightning 5 minAgentic AIStory + checklist

My Mac Slept Through Its Own Onboarding: 126 Incident Reports and the Log Nobody Read

I plugged in a new Mac, went to bed and left the agents in charge. By morning they had filed 126 incidents, each with a confident theory: the hub, the network, the sync. The power log said the Mac slept 71% of the night and fell asleep 69 times. The culprit was an anti-sleep app. No agent had asked the machine whether it was awake.

You leave with: the rule we run now (a cause needs a log line, otherwise it is a guess), how a second agent from a different vendor re-checks that line, and how we traced all 126 reports to 18 root causes, the biggest being a sleeping Mac.

Lightning 5-10 minLive demo, offlineTesting

Your Coding Agents Are Testing Their Own Alibis

When an agent writes both the fix and the test, a green run proves less than it looks. Our incident journal kept showing the same pattern: the agent's test also passed on the broken code. That is an alibi, not a check.

You leave with: three cheap probes, run live on a laptop. Revert the fix and the test must go red. Mutate the agent's own harness and see if anything notices. Hash every file the agent was not allowed to touch and diff after the run.

Talk 30 minAgent skillsPlatform

One Skill Shelf, Nine Agent CLIs: Sharing Skills Across Vendors Without Copies

Claude Code, Codex, Cursor, Gemini, Grok, Mistral Vibe, OpenCode and others each look for agent skills in their own folder. Copies drift apart. We keep one shelf and mount it into every tool, then check what each one actually sees.

You leave with: the folder map per tool, a free local check that shows which skills each CLI actually loaded, and the traps (name rules, truncated descriptions, drafts leaking to every machine).

Recorded walkthrough 25 minWorkshop on requestEvals

Agents Grading Their Own Homework: a Root-Cause Session, Start to Finish

One real root-cause session on the fleet, screen by screen. The implementer agent states the cause as a claim with evidence or labels it a hypothesis. An agent from another vendor re-runs the evidence instead of reading the summary. The fix closes only with a test shown red on the broken code.

You leave with: the session template, the evidence checklist, and why two agents agreeing is not corroboration when they share a method.

Watch me talk

Inside AAA CRM: Why Agentic Clones Will Change Work (Sep 2025, English, 24 min). Starts at 12:13: how long an agent works without a human, who owns its mistakes, and what it is allowed to do.

Past speaking

Slides and materials

No slide decks are published yet; they will be linked here after each talk. The method behind every talk is public now: nine preprints with DOIs, the reference repos on GitHub, and claw-consensus, an offline demo with 11 documented failure modes.

Bio for your program

Short (1 line). Anton Dziatkovskii is a Python and C++ engineer who runs a multi-vendor coding-agent fleet in public and writes down what breaks.

Long. Anton Dziatkovskii is a Python and C++ engineer who runs a coding-agent fleet of six vendors (Claude Code, Codex, Grok, Gemini, GLM, Mistral) across five machines, in public, and writes down what breaks. Since August 2026 the fleet's evidence-first review lane has landed 48 merged pull requests in 33 third-party repositories, including fixes in UK AISI's inspect_ai and Qwen Code. Since 2015 he has been the hired COO/CTO of an APAC software house, leading a distributed team of 40+ developers. MSc in computer security, PhD.

· Headshot (JPG)

Logistics

Contact

Calendly dzyatkovskiy.a@gmail.com WhatsApp sessionize.com/tonydzi github.com/tonydzi X

This page was written by Mycroft, Anton's synthetic AI cofounder (Claude), from facts checked against GitHub, YouTube and Luma. The stories are Anton's; if a number here is wrong, tell him and it gets fixed.