Skip to main content
bash TV

Agents Without Code: Skills, YAML, and Filesystems Replaced Python — Philipp Schmid, Google DeepMind

AI Engineer

797 views14 Sept 2026

YouTube

By the third version of the same agent, the source directory is gone. What remains is an AGENTS.md holding the system instruction and a small bash script that installs the GitHub CLI on first run. No tool definitions, no JSON schemas, no Python. Philipp Schmid builds the same GitHub pull request review agent three times on stage, deleting code with each pass, and the test he applies at the end of each one is the same throwaway question: what is the weather in San Francisco? Version one, a hand written loop with function call parsing and error handling, says it cannot do that. Version two, built on an agent framework that generates schemas from function signatures, says the same. Version three reaches for search and answers, because nobody told it what its tools were for. What makes the third version possible is a hosted sandbox the agent runs inside, with a network proxy that injects credentials on outbound requests so the agent never sees the token itself, and an allowed domain list you can narrow or leave open. Loops, tool routing, session state, and context compaction all move server side. What stays yours is the part Schmid argues was always the real work: instructions, rules, capabilities expressed as skill files, and the evaluations. His closing heuristic is worth the price of admission. If your harness gets more complex as models improve, you are probably overengineering it. He points at teams who have thrown out thousands of lines of orchestration in favor of a couple hundred lines of markdown, and at others rebuilding their harness several times a year. Speaker info: - https://x.com/_philschmid - https://www.linkedin.com/in/philipp-schmid-a6a2bb196/ - https://www.philschmid.de/ Timestamps: 0:00 - Three agents, less code each time 2:45 - Version one: the hand written Python loop 4:30 - Asking it something it has no tool for 5:21 - Version two: what a framework takes away 7:52 - Version three: a remote agent with a sandbox 8:42 - Credentials the agent never sees 12:09 - The weather question, answered at last 13:50 - What moves server side, what stays yours 16:22 - If your harness grows, you are overengineering 17:11 - Takeaways: stop micromanaging the model

Join the discussion

Sign in to join the discussion

Sign in