Running · in daily use

An assistant that does the work, not just the chat.

Poppy is an executive-assistant agent. You send it a request the way you would message a person, and it carries the task through — drafting and sending email, scheduling, running research, even kicking off and shipping development projects — with a memory that persists across every session.

Message Poppy It works out the ask Acts: email · schedule · research · build Reports back
What it is

A standing agent, not a chat window.

Most AI assistants wait for you to open them, answer the question in front of them, and forget everything the moment you close the tab. Poppy is the other shape: a persistent assistant that is always reachable, turns a request into completed work, and remembers what happened so the next request lands in context.

The point is the verb. You do not ask Poppy about your calendar; you ask it to send the invite. You do not ask it to explain a code change; you ask it to make the change and move it from development to production. It is closer to a chief of staff than a chatbot.

Underneath, Poppy reads and writes a structured memory so it knows the state of your work without being re-briefed each time. That memory is Meridian.

You do not ask Poppy about your calendar. You ask it to send the invite.
  • It completes tasks. The output is a sent email or a shipped change, not a suggestion.
  • It is always on. Reach it the way you message a colleague; it does not need to be opened.
  • It remembers. Persistent, structured memory means no re-briefing every session.
  • It defers when it should. When something needs your call, it asks rather than guessing.
How it works

Request in, action out

Every incoming message runs the same loop.

Step 1
Receive

You send Poppy a message in plain language, from wherever you already are. No special syntax, no app to open.

Step 2
Classify

Poppy works out what kind of request it is — a quick answer, a piece of research, a reminder, an email to send, or something that needs your decision — and routes it to the right action.

Step 3
Act

It carries out the task: drafts and sends the email, schedules the invite, runs the research, or starts the development job. Built-in guardrails keep it from acting too fast or too often.

Step 4
Report & remember

Poppy tells you what it did and records the outcome to its memory, so the next request already knows the context. Decisions it cannot make alone are queued for a simple yes or no from you.

What it does

The kinds of work it carries

Email

Drafts and sends email on your behalf, in your voice.

Scheduling

Creates and sends calendar invites and keeps track of reminders.

Research

Runs longer research tasks and comes back with the findings, not just links.

Ships projects

Kicks off development work and sees it through.

Moves work to production

Migrates changes between development and production environments.

Holds decisions

Queues anything that needs your call and resolves it on a yes/no reply.

Why it works

The memory is the difference

An assistant that forgets is just a faster way to repeat yourself.

  • Persistent across sessions. Poppy reads its state at the start of every run and writes back what changed.
  • Structured, not a transcript. Work is organised by project and topic, so the right context is easy to recall.
  • Shared with your other agents. The same memory layer, Meridian, backs Poppy, Ganglia, and the rest of the suite.
  • It asks before it assumes. When it does not know, it looks it up or checks with you — it does not invent state.
Status

Running, and earning its keep

Honest about what this is: Poppy is a personal assistant we built and run for ourselves, not a product for sale. We are showing it because an agent that completes real work — safely, with memory and judgement about when to ask — is exactly the kind of thing our practice exists to get right.