I Stopped Prompting AI One Task At A Time. This Works Better.

Nate B Jones · 2026-06-24

This video introduces the concept of 'loops of loops' in AI, moving beyond single prompts to persistent, memory-aware agents. These agents organize around recurring jobs, reducing human mental load by noticing changes, sharing context, and stopping when human judgment is needed. The core idea is to build interconnected AI agents that automate recurring tasks across different applications, effectively acting as 'loop managers' that handle practical workflows and free up human attention for more critical decisions.

read more

The speaker, Nate Jones, argues that current AI, primarily prompt-based, still places a significant burden on users who must constantly re-prompt, monitor changes, and make decisions. He proposes a 'loop of loops' architecture to address this by having AI lift the mental load rather than adding to it. This concept is distinct from a 'magic life manager' and focuses on practical, recurring tasks.

He clarifies the terminology: A prompt is a single request. A loop is a recurring job with memory that remembers 'what changed' from its last run. A loop of loops occurs when multiple recurring jobs (individual loops) can notice each other, share what changed, and stop when they hit your boundaries (requiring human judgment).

Jones uses the example of managing a school trip. A simple prompt might generate a packing list. However, a 'loop' would automate the recurring aspects: remembering past packing lists, checking weather, finding school emails, and knowing which type of trip it is. This still leaves the human responsible for initiating and overseeing these individual loops.

The loop of loops elevates this by having a 'Trip Loop' as the orchestrator. When a 'Trip Notice' (new event) signal comes in, it wakes up relevant individual loops: the 'Packing Loop' (checking owned items), the 'Weather Loop' (checking for rain), the 'School Schedule Loop' (noticing a pickup time change), and the 'Calendar Conflict Loop' (identifying a meeting conflict). This chain of awareness allows the system to proactively identify potential problems.

Crucially, these loops are designed to hand off context to each other and bring the human into the process when judgment matters. For instance, the 'Calendar Conflict Loop' might trigger a 'Message Loop' to draft a text to another parent about pickup changes, but it 'stops before sending it' for human approval. This is about self-organizing workflows, not fully autonomous AI taking over, providing a safe action framework where known facts (world state) and defined boundaries lead to approved moves.

Jones emphasizes that most useful work is a recurring situation with memory, not a single question. This is where traditional apps have failed us, as they provide digitized pieces of a workflow but require the human to do all the 'wiring in between' by manually opening different apps (email, calendar, grocery list) and connecting the information.

The first useful AI agent, according to Jones, will sit between apps across the various loops that constitute our daily mental load. He encourages engineers to identify the hidden state (the load carried in your head) associated with their own recurring jobs. This involves understanding: what changed (signals), what's in progress (drafts), what needs quality checks, and what's waiting/blocked. The goal is to make as many loops as possible 'run cleanly' without human intervention, so you only get 'woken up' if it really matters, managing your attention budget effectively.

Examples of potential loops include: a 'Sales Loop' remembering call details, objections, and pricing questions; a 'Support Loop' tracking unresolved issues; or a 'Research Loop' monitoring AI news from Twitter and Google, aggregating themes, and presenting a concise perspective. Another example is a 'Kids Clothing Size Loop' that remembers past purchases, notices seasonal changes, tracks child growth, and nudges the parent to size up before it becomes an urgent problem, thus catching problems early.

Jones concludes by encouraging a shift in thinking: instead of just prompting AI, think about loops and loops of loops as a way of allocating your attention once to build something useful. He stresses that the difference between prompting and getting into 'loop space' represents 99% of your mental effort saved. The key is to define the 'world state' your agent should engage in, a set of 'safe choices' for it to reason through, and an 'approved move' it can take, all within boundaries you define. The initial implementations should focus on tedious but not incredibly impactful tasks, allowing for experimentation and learning without high stakes. He explicitly advises against banking for initial implementations. By externalizing these recurring mental loads into AI loops, engineers can achieve exponentially lighter workloads and focus on higher-value activities.

Is it ever coming back?

Theo - t3.gg · 2026-06-24

This video details the unexpected ban of Anthropic's Claude Fable 5 and Mythos 5 AI models, initiated by a US government export control directive. The ban, stemming from allegations of a potential narrow, non-universal 'jailbreak' and concerns over a South Korean firm reselling access to China, highlights a significant shift in AI regulation. This event has caused delays in other AI model releases, spurred legal action against the US government, and raised critical questions about the future of AI development, intellectual property, and international collaboration in the tech industry.

read more

On June 9th, Anthropic released its Claude Fable 5 and Mythos 5 AI models, which were described as incredibly powerful. However, just three days later, on June 12th, the US government issued an export control directive, immediately suspending access to these models for all foreign nationals globally, including Anthropic's own non-US employees. This decision was based on claims of a 'potential narrow, non-universal jailbreak' that would allow the model to read and fix software flaws, a capability the government deemed widely available in other models (including OpenAI's GPT-5.5) and used daily by defenders to keep systems safe.

The initial press release from Anthropic promised more details within 24 hours, which never materialized. The managing director of Anthropic's international division also expressed confidence in a quick re-enabling of access, but after 11 days, the models remain unavailable with no clear timeline for their return. This has sparked widespread concern and action across the tech and political landscapes.

Several entities are pushing back against the government's directive. Bipartisan members of Congress have sought transparency from the Department of Commerce regarding the June 12th decision, citing concerns that it sets a significant new precedent for frontier AI regulation. Additionally, a US-based AI-native litigation-technology company named Legion has filed a 43-page lawsuit against the United States, the Department of Commerce, and other officials. Legion, a commercial customer of Anthropic, claims the directive is unlawful and exceeds statutory authority, violating prohibitions against restricting the export of informational materials under the International Emergency Economic Powers Act (IEEPA).

The controversy appears to have originated from allegations that SK Telecom, a South Korean company that invested heavily in Anthropic and partnered to develop AI models for the telecommunications industry, was reselling access to Claude Mythos to customers in China. While the US government reportedly told Anthropic to revoke SK Telecom's access without initially threatening export controls, this incident evidently put the government on high alert regarding the models' capabilities and international access. Anthropic's compliance, despite the significant investment and partnership with SK Telecom, further complicated matters.

This situation has had broader implications, including delays in other significant AI model releases. For instance, GPT-5.6's release has been delayed until mid-July, and DeepMind is reportedly dissatisfied with its current 3.5 Pro model. Anthropic itself is reportedly working on a cheaper, dumber version of Claude Sonnet 5 as a stop-gap measure for affected customers. The general sentiment within the AI community is one of fear and uncertainty, with concerns that future AI advancements could face similar restrictions or outright bans. The video highlights a perceived dissonance between the government's interpretation of a 'jailbreak' (which seems to be the model's intended ability to analyze and fix code) and Anthropic's view of it as a core functionality.

The speaker emphasizes the danger of a precedent where governments can restrict access to AI models based on subjective interpretations of their capabilities, especially when similar capabilities exist in open-weight models. The distinction is crucial: models with fewer restrictions incentivized by a less regulated environment (like potentially in China) could gain dominance if US-based models are unduly constrained. The fear is that the US government, by imposing such broad restrictions, is inadvertently hindering domestic AI innovation and pushing development towards less regulated environments. The speaker concludes by stressing the importance of protecting critical infrastructure and ensuring US leadership in AI through transparent and evidence-based regulation, rather than restrictive bans that create uncertainty and impede progress.

Finally, the speaker references Artificial Analysis, which indicates that Claude Fable 5, with an Intelligence Index of 60, was the best model available, significantly outperforming others. This capability, particularly in code work, makes its ban all the more impactful, especially when open-weight models like GLM-5.2 are rapidly catching up to the capabilities of models like GPT-5.5. The speaker warns that stifling access to powerful models for legitimate development uses sets a dangerous precedent, making it harder for developers to build innovative tools and ultimately impacting the global AI landscape.

datasette 1.0a35

Simon Willison · 2026-06-23 · 2 min read

Datasette 1.0a35 adds full create and alter table functionality via both a web UI and JSON APIs, letting you define schemas, modify columns, manage constraints, and drop tables directly through Datasette rather than raw SQL tooling. For a senior engineer, the notable part is that the template context variables are now formally documented as a stable API contract through Datasette 2.0, with that documentation auto-generated from dataclasses and verified by tests — a meaningful signal that the project is hardening its extension boundaries ahead of a stable 1.0 release.

The "55x faster coding" claim misses the whole point

Beyond Coding · 2026-06-23

This video argues that while early discussions around AI for software engineering focused on productivity and code completion, the true potential lies beyond these initial gains. The speaker suggests that as AI agents and models become more powerful, the focus should shift towards improving code quality and accelerating the pace of innovation. By freeing up developers' time from routine tasks, AI can enable them to learn more, understand these agents better, and ultimately add more value through innovation.

XEmacs is Dead. Long Live XEmacs!

Steve Yegge · 2008-04-28 · 59 min read

TLDR: XEmacs was a historically important fork that dragged GNU Emacs into the modern era with GUI features and faster development, but its chronic instability made it unsuitable for power users who live inside their editor full-time. For casual users who open-edit-close, the crashes are a minor annoyance; for serious Emacs inhabitants who never restart their session, that instability is a fundamental dealbreaker that GNU Emacs — with its slower but more disciplined development — never suffered from.