Skip to content

AutoMinds / Our story

Built around
a human
question.

What makes a good colleague? That question shapes everything we build.

Meet the mind behind AutoMinds
Ami, the curious celadon character of AutoMinds
A little curiosity goes a long way. Meet Ami.
Human judgment. Agent intelligence.Los Angeles, California

The question that stayed.

I wrote code before I could drive. It was a way to hold an idea exactly as I meant it.

In college, I studied neuroscience and psychobiology. I kept coming back to attention, memory, and judgment. How does a mind decide what matters? How does a small team see something a much larger one misses?

Those questions followed me into AI. An agent could answer a question and still lose the thread of the work. It could execute a task without understanding why that task mattered.

The thing I kept rebuilding.

AutoMinds started with a pattern: I kept needing agents that could hold context, maintain a role, and coordinate with one another. Each new system brought me back to the same foundations.

That became the work of the company. We build agent teams with clear responsibilities, useful memory, and deliberate handoffs. We design the points where they act, where they check their work, and where a person makes the call.

Small teams, with room to think.

A lot of work disappears into repeated briefings, lost context, and handoffs that need another meeting. Better coordination gives people more room for judgment.

That is the future I want to build: small teams supported by AI colleagues that carry their part of the work, with people responsible for the direction.

Read the workforce thesis

How we build

Good colleagues.
By design.

The same principles guide a research agent, a commerce workflow, and the systems that connect them.

01

Carry the context.

Keep the goals, constraints, and decisions close to the work. A useful handoff should not require starting over.

02

Make the work legible.

Show the evidence, the next action, and what remains uncertain. People need a way to inspect and correct the system.

03

Know when to ask.

Give agents clear boundaries. Bring people in when the evidence is incomplete or the decision is consequential.

From the idea to the work

See what this
looks like in practice.

Explore the systems we build and the thinking behind the decisions.