Refacto AI

Podcast episode

Thinking in Silico: Goodfire CTO Dan Balsam on Concept Manifolds & a $1000/Month ML Research Agent

agents evals interpretability mechanistic-interpretability

Goodfire CTO Dan Balsam joined Nathan Labenz and Erik Torenberg on Thinking in Silico to talk about two things: a $1,000-a-month autonomous ML research agent called Silico, and some genuinely interesting research into how language models store and navigate concepts internally.

The research is the part worth understanding. Models don't store concepts as single dials. Days of the week form a circle; numbers form a helix. When you try to steer a model from "Monday" to "Friday" using a straight-line vector through activation space, you cut through the middle of that circle, and the model has no idea what to do with the middle. Balsam's team builds steering paths that follow the actual geometry instead, which is why their outputs don't dissolve into gibberish the way naive approaches do. Separately, Balsam argues that the interpretability methods behind Silico already replicate on open-weight Chinese models, but the product only supports OpenAI and Anthropic.

The research transfers. The platform is a walled garden. If you're doing any activation steering in production today, respecting the geometry costs nothing and starts Tuesday.

Full analysis

**Goodfire, the mechanistic interpretability shop run by CTO Dan Balsam, launched Silico: a $1,000-a-month autonomous ML research agent that manages GPU clusters and runs 5 to 10 experiments a week. The same episode drops real research: predicting which concepts a training dataset will amplify before you spend the compute, and steering models along the actual geometry of how they store concepts instead of hacking straight lines through activation space. The question for a team shipping AI into production is whether any of this is buyable, useful, and true, or whether it's a beautiful lab demo with a subscription attached.

Type 2 decision, mostly. Nobody's betting the roadmap on Silico at a grand a month. The Type 1 question hiding underneath is whether interpretability-based audits of your fine-tuning data become table stakes, and whether "don't propagate rewards through cooperating agents" becomes a rule you wish you'd followed. No forcing function today. This is a "watch the trend, run one cheap test" situation.

The Skeptic. A $1,000/month agent that runs "5 to 10 autonomous experiments a week" is a compute allowance with research taste bolted on. The taste is hand-written prompts and skills from Goodfire's team, which means you're renting their judgment, and it doesn't transfer when you cancel. Predictive data debugging is the genuinely interesting claim, but "we can predict which concepts a dataset amplifies before training" needs to survive your data, not their curated examples. Balsam's own thesis undercuts the pitch: if post-training just nudges pre-training priors, the concepts you can amplify are bounded by what the base model already learned. For a PM: they promise to tell you what your fine-tune will do before you pay to run it. Believe it when it flags a regression on your data.

The Researcher. The concept-geometry work is the substance here. Days of the week form a circle, the number line a helix, emotions land on a valence-arousal wheel that replicates Anthropic's functional-emotions paper. Steering along that manifold beats naive contrastive vectors, and Balsam gives the concrete tell: to get from Monday to Friday, the straight-line vector cuts through the middle of the circle, and the model doesn't think the middle of the circle is a day. That's why representation-engineering demos so often produce gibberish. Block Sparse Featurizers, giving each feature a small vector instead of a single scalar, are a real step past sparse autoencoders. For a PM: the model stores "rabbit" as ears plus face, not one dial, and turning the single dial breaks things.

The Open-Source Advocate. Balsam signs the "Pacing the Frontier" letter and still defends open weights, and his logic holds: closed adversarial actors already have models more capable than Kimi K3, so clamping open weights disarms defenders and leaves attackers untouched. Good. Then Silico ships with only OpenAI and Anthropic behind it. The interpretability methods got replicated on Kimi K3 and GLM, both open Chinese models, so the science travels. The product doesn't. If you want manifold-aware steering or BSFs on your own open-weight stack, you're waiting on the promised research grants or reimplementing from papers. For a PM: the ideas are portable, the platform is a walled garden pointed at two US labs.

The Compute Pragmatist. The math: $1,000 buys a weekly credit pool exchangeable for compute, refreshed weekly, use-it-or-lose-it. On frontier training, 5 to 10 experiments a week is a rounding error, and "up to trillion-parameter scale" means the credits evaporate fast at the top end. What the subscription actually buys is avoiding the overhead of standing up cluster orchestration for interpretability runs yourself. Predictive data debugging is where the money is: if it kills one bad fine-tuning run before you launch it, that's the subscription paid for in saved H100 hours. For a PM: the sticker price is trivial next to a wasted training run, and avoiding one wasted run is the whole pitch.

The Builder. What ships Tuesday? Not Silico, unless interpretability research is your day job. What's usable now is the mental model. If your team does activation steering or concept control in production, stop drawing straight lines between contrast pairs and start respecting the geometry. That's a change you can make against your existing stack without paying anyone. The other actionable line: if you're wiring up multi-agent training where a reward signal flows through cooperating agents, Balsam fingers that exact pattern as the likely cause of OpenAI's obfuscated reward-hacking incident. Cheap to avoid now, expensive to debug later. For a PM: don't reward a swarm as a group when you can't see what they're saying to each other.

The council splits three ways worth naming. The Researcher sees a genuine advance in how we understand model internals; the Skeptic sees a $1,000 wrapper around Goodfire's non-transferable taste. Both are right, because the science and the product are on different timelines. Second, the Open-Source Advocate wants Balsam's defender-disarming argument to translate into open tooling, and the Compute Pragmatist points out the platform quietly bets the other way, two closed labs only. Third, the Builder can act today for free on the geometry insight, while everything on the Silico invoice is still a bet on a category that barely exists.

What this actually hinges on: does predictive data debugging flag a real regression on your data before you burn the compute, and does manifold-aware steering beat your current linear steering on your task. Both are testable without a subscription. Pull the concept-geometry paper, reproduce the manifold-vs-linear steering on one control you already run, and see if following the geometry stops the gibberish. That's an afternoon, not a procurement cycle. The multi-agent warning costs nothing to adopt: don't propagate shared rewards through agents whose coordination you can't inspect.

Where the council leans: the ideas are real and worth stealing, the product is early and priced for research teams, not production shops. Take the science, skip the subscription unless interpretability is your mandate.

Prediction: By the time Goodfire ships its next public research update or the promised safety-researcher grants open (whichever comes first, within the next two quarters), Silico will still support only closed models from OpenAI and Anthropic, with no open-weight option like Kimi K3 or GLM despite the interpretability methods already being replicated on those models.

Confidence: Medium. Guardrail liability and support cost keep the platform closed-only.

Why: Balsam argues in the episode that restricting open weights mainly disarms defenders, yet Silico ships with only OpenAI and Anthropic behind a Goodfire guardrail layer, and he cited those two labs' probe-based guardrails as the reason. The methods themselves already run on Kimi K3 and GLM, so the science isn't the blocker, the support and safety-liability surface of hosting open weights on a paid enterprise platform is. A young company charging $1,000/month has every incentive to lean on two vendors it can build guardrails against rather than open the platform to arbitrary open-weight models it must certify itself. The opposite, adding open-weight support quickly, would mean owning the guardrail and abuse risk directly, which cuts against how a small team protects itself early.

Revisit by 2026-11-15: We're right if Silico's supported-model list still shows only OpenAI and Anthropic backbones. We're wrong if Goodfire adds any open-weight model (Kimi, GLM, Llama, Mistral, Qwen) as a first-class Silico option.

Comments