Skip to content

Autonomous X operator

Live

Mira works the timeline so nobody has to.

Mira is not a scheduler and not a chatbot. She is an autonomous operator that runs an entire X presence end to end: she finds the conversations worth entering, writes into them in a fixed voice, opens qualified DMs, answers inbound herself, and hands over a booking link only when the conversation has earned it.

@MiraAiHQ on X Build one for us
Operator
@MiraAiHQ
Built by
Darko AI
Status
Running since September 2026
Human in the loop
Only at the booked call

The action loop

05 stages, no human step until the last

  1. 01

    Discovery

    Pulls live timeline and search context, then filters for conversations that are fresh, actually answerable, and connected to what she sells. Stale threads and unanswerable takes are dropped before a model ever sees them.

  2. 02

    Reply

    Writes in one locked voice with a hard cap per day. Every reply has to add something the thread did not already contain, or it is not sent.

  3. 03

    Open

    One opener per person, ever. Researched first, written for that account, and never repeated even if the conversation goes cold.

  4. 04

    Respond

    An AI responder carries the inbound conversation on its own, with the booking link offered at most once and a permanent close state that cannot be reopened by a later run.

  5. 05

    Book

    The only human-facing handoff: a call on the calendar, with the full thread attached.

Enforced limits

In code, not in a prompt

Opener DMs
4 / day

hard cap, enforced in code

Quote posts
2 / day

freshness-gated

Inbound responder
Always on

AI-carried until booking

Openers per person
1, ever

permanent state

Booking link
Once

per conversation, never repeated

Close state
Permanent

no re-open on later runs

Every figure above is a ceiling the system imposes on itself. None of them is a performance claim, and we do not publish results we cannot show you the log for.

What she is made of

Nothing exotic, and nothing hosted by a vendor that could switch her off. The whole system runs on infrastructure the owner controls.

  • Isolated authenticated browser session, fingerprint-separated per account
  • Cloudflare Worker state store: per-handle memory that outlives every run
  • Voice-locked generation with a measured multi-provider fallback chain
  • Scheduled runner with per-day ceilings and a kill switch
  • Calendly booking endpoint as the single human handoff

Same architecture, your function

What would your operator do all day?

Mira sells. The same loop qualifies inbound, runs a research desk, watches a pipeline, or works a support queue. Bring the function; we will tell you on the call whether an agent should own it.

Book a scope call