with-agents

ZiP — Salvatore Sanfilippo & Enkk

AGI, benchmark e altri spinosissimi problemi: ZiP 5

AI capabilities, evaluation, local models, and social implications

A combined episode guide to Salvatore Sanfilippo and Enkk's Italian-language conversations across both channels: coding-model workflows, local inference, AI safety, interpretability, text watermarking, AGI labels, and evaluation through useful work. The guide records summary coverage because the hosts' separate YouTube playlists are incomplete. Opinions, proposals, and project anecdotes are not controlled evaluation results.

Salvatore Sanfilippo & Enkk Episode 5 1 of 5
Episodes Browse 5 summaries 1 of 5

Salvatore Sanfilippo and his ZiP co-host ask what an artificial general intelligence (AGI) label actually changes for people using models. Their practical answer is that stronger capabilities do not remove uneven performance, hallucinations, or the need to evaluate the work you intend to delegate.

Capability is not a blanket guarantee

  • An AGI label does not justify lowering your guard: The speakers describe progress across different abilities, not a single moment when a model becomes reliable at everything. Sanfilippo argues that a model could make scientific discoveries or invent algorithms while still giving invented answers to other questions 02:11–08:35(opens in a new tab).
  • Encouraging an attempt can also encourage an unsupported answer: Sanfilippo describes a training tradeoff. Encouraging an assistant to attempt tasks despite uncertainty can help it solve problems it would otherwise abandon. But the same encouragement can push it to answer when it lacks the knowledge, rather than admit that it does not know. In his account, greater capability does not necessarily remove hallucinations 06:26–08:35(opens in a new tab).
  • Confidence must stay task-specific: They use contrasting forms of human intelligence to explain uneven model abilities, then point out that a model can shift between competence and failure even on similar problems. Repeated programming experience can build useful confidence, but one successful answer does not establish competence everywhere 51:23–54:25(opens in a new tab).

Persistent state raises different questions

  • Text notes preserve earlier work by putting it back into context: In the workflows they describe, an agent saves notes, retrieves history, or shortens the conversation into a summary. That information helps when it is included in the model's current context—the input available for its next response 11:50–13:43(opens in a new tab), 18:43–19:41(opens in a new tab).

  • Sanfilippo imagines memory carried over inside the model: He proposes an additional numerical representation of earlier work, updated as the model works and retained when its context changes. Later reasoning would depend on both the current input and this retained state. In his example, identical input could lead to different behavior because the internal memory differs 13:43–14:33(opens in a new tab).

    His compiler example explains the intended benefit: keep the overall goal of building a compiler in view while working on an immediate task. Notes can also preserve that goal; the proposed difference is retaining information internally rather than supplying it again as text. This is a speculative architecture, not a demonstrated way to keep a model focused on the right goal 14:33–18:43(opens in a new tab).

  • Persistent internal state could make oversight harder: The speakers worry that models with retained internal state would be harder to monitor. Sanfilippo would rather reach useful capabilities with models that run when asked and can be stopped than build systems resembling human minds 21:32–24:34(opens in a new tab).

    They disagree about what would justify concern for an artificial system's experience, including whether biology, sensory input, and acting without an external prompt matter. They distinguish representing an emotion internally from actually feeling it; the debate provides no test that establishes consciousness or suffering 27:40–50:18(opens in a new tab).

Evaluate useful work, but keep diagnostic tests

  • Discovery and engineering output could become stronger capability signals: Sanfilippo predicts that frontier models will increasingly be judged by new science and technology they help create. His co-host counters that conventional testing still matters for prompt injection, alignment, and finding where models succeed or fail—including across repeated interactions and the steps an agent takes toward a goal 1:02:32–1:06:46(opens in a new tab).
  • Measure improvements to real projects: Sanfilippo proposes asking models to make Redis faster and reduce memory use while still passing every test. He also suggests comparing models on measurable improvements across open-source projects. These are proposals, not completed comparisons 1:06:46–1:07:47(opens in a new tab), 1:14:55–1:15:58(opens in a new tab).
  • A measurable score can become a training target: His co-host argues that, once success can be checked automatically, developers can use that check to train models through reinforcement learning. Longer tasks do not remove the difficulty: varied tasks are harder to create, models may exploit the scoring rules rather than fulfill the intended goal, and outcomes such as marketing results may take a year or two to observe 1:07:47–1:09:56(opens in a new tab).
  • Distinguish newly achievable work from an impressive demo: Sanfilippo bases his favorable model judgments on making progress with optimizations that had resisted earlier models, citing Redis and Dwarf Star projects. Those are first-person reports, not controlled comparisons. Both speakers criticize generic one-shot demos as weak evidence for meeting a real project's particular requirements under human direction 1:17:00–1:21:07(opens in a new tab).
  • Give independent evaluators enough time: They criticize launch practices that give influencers early access while, according to their reading of evaluation reports, independent safety assessors receive insufficient testing time. This is their account of the reports, not an independent audit of the release process 1:21:07–1:23:13(opens in a new tab).

Editorial takeaway: Judge a candidate model on representative work with explicit correctness and performance checks. Treat capability gains, safety behavior, and persistent-state design as separate evaluation questions rather than collapsing them into a single AGI claim.

Watch the full discussion on YouTube(opens in a new tab). In the subtitle menu, select English (US) for the English caption track.

More ZiP: Episode 4 and the combined episode guide link both hosts' playlists and the earlier episodes, with current summary coverage.

Search

Search field guides and resources across the site.

    Keyboard shortcuts

    Press ? to open this guide (usually Shift + /). Close it before using other site shortcuts.

    Show keyboard shortcuts
    ?
    Search site
    Ctrl + K
    Close the current dialog or menu
    Esc

    Site shortcuts are ignored while typing. Browser and extension shortcuts may take priority.