Waldo

For many well-scoped tasks, machines can now produce plausible code, documents, plans, and analyses in minutes. The cost has not disappeared. It has moved into understanding assumptions, reconciling contradictions, reviewing consequences, and knowing whether the work changed anything that mattered.

I first felt this while building and operating more than 30 production agent instances at Atlan. Starting another run was easy. Remembering why it existed, moving context between tools, detecting a waiting decision, and checking whether the original problem was actually resolved remained human work.

Suyash encountered the same structure while running a design studio and training for an Ironman: more tools could produce more information, but no system could reliably decide what mattered now, what could wait, or what no longer deserved to be carried.

The transition is larger than coordination. Capability is becoming abundant while comprehension, attention, legitimate authority, and accountability remain finite. That is the constraint system Waldo is investigating.

AI is not creating one neatly contained problem. It is producing a reinforcing pool: more output raises evaluation load; more agents raise management work; fragmented memory raises reconstruction; easier action raises governance and consequence; cheaper intelligence raises the need to decide what the spend actually bought.

The center of gravity is epistemic. Waldo should help a person know what is true, what changed, what remains, and why—not orchestrate for its own sake. Coordination, memory, and interfaces are candidate means.

One human intention can span many sessions, specialist agents, tools, people, and days. Provider memory can preserve a transcript; it does not necessarily preserve why the work exists, what changed the plan, what was accepted, or which consequence still remains.

Responsibility continuity is our current hypothesis for that connective tissue. Waldo should retain the desired result, current constraints, authoritative sources, corrections, decisions, unresolved consequences, and the smallest truthful re-entry point—even as the executor changes.

This does not mean giving everyone an operator console. The person should not inherit the skill of managing an agent fleet. Waldo should compress routine discovery, briefing, monitoring, reconciliation, recovery, and re-entry, then surface uncertainty, changed scope, irreversible effects, cost, or permission only when human judgment is truly required.

The hypothesis remains replaceable. If native providers absorb this burden, if people prefer direct control, or if the representation creates more cognitive load than it removes, Waldo must change rather than defend the label.

Kennel, a durable harness, and Waldo mobile are working internal foundations. Their integration, external product behavior, and market validation remain open work.

Kennel has the strongest internal acceptance record: attributable Codex sessions, conversation history, live processing state, same-task continuation, first-message handling, and archive cleanup.

We start with Kennel on the Mac, where the problem is already acute for people running multiple coding agents. Kennel absorbs session-level coordination and brings back what changed, what is supported by evidence, what needs judgment, and what remains open.

Waldo is the layer above it: one private, user-owned personal agent designed to carry intent, context, permissions, memory, commitments, and responsibility across agents, tools, work, and life. Models and interfaces can change; Waldo remains on your side.

Your life and your agents should not belong to two different systems. Personal assistants and work orchestrators have evolved as separate products, even though the user is the same person. Calendars, messages, reminders, commitments, and daily administration should not belong to a different identity from the sessions, runtimes, tools, budgets, and policies involved in getting work done.

I don’t believe one model or interface will own our entire digital life. People will use many models, specialist agents, tools, services, and devices. Waldo is being designed to join personal assistance and work orchestration around the same Outcome, authority boundaries, source material, and continuity.

An organization may own some infrastructure. The individual should own the continuing relationship. Models, tools, employers, and surfaces can change; the context a person chooses to share, their permissions, corrections, responsibility history, and unresolved work should remain with them.

The models may be rented and replaceable. What should compound for the person is their context, corrections, permissions, procedures, responsibility history, and accepted outcomes. Waldo is being built to keep that intelligence on the person’s side even as the machinery underneath changes.

Over time, that same relationship can move beyond the chatbox into mobile, voice, wearables, ambient devices, and eventually physical interfaces. Those are presences of one user-owned personal agent—not disconnected assistants that make the person rebuild context every time. One agent. Many presences. Still yours.

An agent waiting five minutes is inexpensive. A person reconstructing context across five agents, reviewing unchecked changes, and finding the correct terminal is expensive. Infinite machine capacity does not create infinite human attention.

Burnout is not a feature category. It is a product constraint: Waldo should not make people supervise more software, monitor more feeds, or remain permanently available. It should carry routine responsibility quietly and return only when timing, consequence, or authority belongs to the person.

Success means less mental reassembly, fewer silently decaying commitments, a realistic next action when capacity changes, and permission to decide that enough is enough.

ChatGPT or Claude can answer what you ask. I want Waldo to understand why you need it, when it matters, what it affects, and whether it was actually resolved. The current prompt is only one fragment of a person’s priorities, relationships, boundaries, capacity, corrections, and commitments.

Life is already distributed across calendars, messages, files, health systems, models, tools, and other people. Waldo should help carry it forward without making the person rebuild themselves—or become the integration layer—every time the interface changes.

The chatbox made intelligence available. It cannot be the whole interface for asynchronous work, and ordinary people should not have to become natural-language programmers or agent managers to benefit. The next layer is continuity, timing, permission, and closure: proactive enough to prepare what matters, but never presumptive about consequential action.

More execution should never mean less agency. We are building Waldo’s working foundations and target architecture around a human rule: continuity must be inspectable, correction easy, and authority fail closed.

Waldo should learn from what a person says, the corrections they make, and outcomes they confirm. Explicit self-knowledge should outrank behavioral inference; activity should never become a hidden personality score.

I see three connected pressures, but I do not treat them as three equal markets. AI-output overload is the customer problem we can attack now through Kennel. Burnout and finite human capacity are the constitution for how Waldo should behave. Physical AI is the expansion horizon where the same questions of permission, interruption, and recovery become more consequential.

The confidence is different too: the overload and burnout problems are already visible; the physical-world tailwind is strong, but Waldo has not yet validated a hardware product or customer wedge there. The wider curve is consumer: capable intelligence is becoming cheap enough to move agents from specialist tools into everyday products.

Notion’s 2026 workplace survey offers a useful directional signal: 88% of respondents placed themselves or their organizations in its thought-partner or assistant stages, while 71% of AI Users said they would use AI more if they trusted it not to make mistakes on important work. Among more advanced users, automation and cross-tool routing rose—but so did tool sprawl, difficulty seeing real impact, and inconsistent model performance. For surveyed decision-makers, the largest implementation gaps between early and advanced groups were integration, governance, and defined measurement. That is the opportunity Waldo is building toward: not more access to AI, but a person-owned layer that makes distributed AI work coherent, governable, and easier to inspect.

Steve Jobs and Steve Wozniak helped turn computers from something hobbyists operated into something ordinary people could make part of their lives. I see agents at the same interface transition: the capability exists, but using it still asks people to think like operators.

Today, the personal-agent stack still asks people to assemble models, repositories, memory systems, skills, scheduled jobs, credentials, and agent harnesses. This is the Apple I moment. Waldo’s job is to turn that machinery into one understandable relationship: give it a responsibility, and return only when judgment or permission belongs to you.

A line Jobs wrote about the Macintosh stays with me: “It’s our job to make complex technology easy to use and fun to use.” Waldo is my attempt to do that for agents without hiding intent, consequence, control, or who remains responsible.

I keep returning to bodies for AI: physical forms people would actually welcome into daily life—a desk object, wearable, home device, vehicle, or small robot. The same Waldo should inhabit each of them, carrying one identity and permission system instead of making every object another disconnected assistant.

The physical-AI tailwind is strong, but this is not a current Waldo hardware program and we have low current customer validation for it. Software comes first because identity, correction, permission, interruption, revocation, and recovery must work before a personal agent is trusted with sensors, movement, or physical authority.

Health and body context is optional and permissioned: a person may choose to share it, but it is neither Waldo’s product category nor a prerequisite. The form may change. The person it works for should not.