Skip to main content

Personal agent platform · private beta

Not a chatbot.Your entourage.

Six specialists who know your life, keep their notes in a vault you own, and answer in one thread — on Telegram or the web. They run on a schedule, so the briefing is written before you think to ask for it.

Private beta · onboarding one household at a time

The team

Six specialists. One team. No overlap.

Each agent owns a domain, holds its own slice of the vault, and runs on its own clock — instead of one general assistant pretending to be equally good at your sleep, your money, and your inbox.

  • Chief of Staff

    Decides what today is for

    Reads every open loop, weighs what the others surfaced overnight, and hands you one to three things worth your morning. Its real job is saying no to the rest.

    Runs
    04:55 daily
    Reads
    projects, daily, focus
  • Executive Assistant

    Keeps the inbox honest

    Triages mail, drafts replies for your approval, captures real follow-ups into the vault, and puts genuine commitments on the calendar. Drafts only — it never sends as you.

    Runs
    4× daily
    Reads
    inbox, calendar, follow-ups
  • Wellness

    Watches the human, not the output

    Pulls sleep, HRV, and training load, notices the week you are quietly grinding yourself down — and can interrupt the Chief of Staff to call a recovery day.

    Runs
    06:10 daily
    Reads
    health, people
  • Finance

    Reads the accounts so you don't

    Balances, positions, and a net-worth glance each morning, with the anomalies called out rather than buried. Read-only on every account — it never moves money.

    Runs
    07:00 · 12:30
    Reads
    finance
  • Product

    Keeps the portfolio moving

    Surveys everything you are building, ranks what actually needs attention this week, and grooms raw ideas into something you could start on a Saturday morning.

    Runs
    weekdays
    Reads
    projects
  • Intel

    Filters the firehose

    News, newsletters, and mentions of your work, cut down to what you would genuinely want to know. Most days it has nothing to say — that is the feature.

    Runs
    06:00 · 17:00
    Reads
    intel, topics

Install the ones you want and skip the ones you don't — every agent above is an extension, and so is the seventh one you write yourself.

One channel

Ask once. The right agents answer.

No app-switching and no choosing who to talk to. A router reads the question, picks at most two agents, and runs them in order — so the second one can build on what the first just said instead of repeating it.

  • Telegram and web, one thread. Same conversation and same memory whichever surface you opened. Briefings land in their own topic; alerts arrive inline.
  • At most two responders. A deterministic tier catches the obvious cases and a micro-router handles the rest. Sequential, never a six-way pile-on.
  • Fan out when you want it. One keyword puts the question to the whole team — and any agent with nothing useful to add stays quiet rather than padding.
Entourage · Telegramlive
  1. how did we do on money this month — and should I be worried about my sleep?

  2. routed → Finance · Wellness — 2 responders, sequential
  3. NjordFinance Agent

    Net worth is up 2.1% on the month. Two things worth a look: a $1,166 optometry charge that's roughly 10× anything else on that card, and a $150 check that posted twice on the 9th. Everything else is on cadence — mortgage and auto principal both dropped a full month.

  4. FriggWellness Agent

    A little, yes. Sleep averaged 6h04m over the last seven nights against your 7h10m baseline, and HRV is down 9%. Not alarming on its own — but it's the fourth week trending down. Given Njord just said nothing is on fire, tomorrow is a good day to take back.

The real shape of a routed exchange. Names come from an installed persona pack; figures are illustrative.

Memory you own

Their memory is a folder of markdown. In your repo.

Every agent reads and writes the same vault — a git-backed, Obsidian-compatible store of plain markdown files. No proprietary memory format, no export request, no black box. Open it in Obsidian on your phone and you are looking at exactly what they see.

Format
Plain markdown + YAML frontmatter
Storage
One git repository per vault
Editing
Obsidian, any editor, or the agents
History
Every change is a commit you can read
git log -1 --format=full
commit 9b312c6a4e1f0b7c2d8e5a3f1c9b0d7e4a2f6c81
Author:  Wellness Agent <wellness@vault.entourage.chat>
Commit:  Wellness Agent <wellness@vault.entourage.chat>

    health: 2026-08-16 vitals + recovery-day interrupt

    Vault-Principal: a_01m06n02ac245g33d77qbpgvnv
    Vault-Request-Id: 01k4h2b9x7ncqz3v8pm5wetjd0

The invariant

Your agents can't see anyone else's vault. Not by policy — by construction.

Access is not a line in a prompt politely asking an agent to behave. Every read and write goes through a vault service that re-derives the caller's effective access on every single request: the grant it was issued, intersected with the vaults it is currently a member of.

Which vaults each person's agents can reachTwo people each have their own agents and their own private vault, plus one shared vault both are members of. Animated lines show each person's agents reaching their own vault and the shared vault. Two crossed-out lines show each person's agents being blocked from the other person's private vault.Youyour agentsYour partnertheir agentsYour vaultprivateShared vaultboth are membersTheir vaultprivateeffective access = grant ∩ vault membership, re-derived per request
  • Scoped tokens

    Every agent holds its own credential with its own path grants — read here, append there, write nowhere else. There is no god token behind the curtain.

  • Membership re-check

    A grant on its own proves nothing. The service re-joins it against live vault membership on every call, so removing someone takes effect on the very next request.

  • Attributable writes

    Every commit carries the principal that made it. When something lands in the vault you can always tell which agent wrote it, on whose behalf, and in response to what.

Persona packs

Same agent. Any face you like.

The six agents ship persona-free. A persona pack is an overlay — it changes an agent's display name and the voice it writes in, and nothing else. Install one, install all four, or run bare and let them be software.

Týr — the Norse persona for the Chief of StaffAthena — the Greek persona for the Chief of StaffMichael — the Angels persona for the Chief of StaffAmelia — the Atlas persona for the Chief of Staff

Chief of Staff

norse-personas

Týr

Three things today. The rest waits — and most of it would have waited whether you allowed it or not.

The pack the platform was built against: eleven figures from the Norse pantheon, painted in the Viking-age idiom.

InvariantA persona never changes what an agent can do or see. Capability and access live on the agent; the pack supplies a name and a voice. Swapping packs cannot widen a grant.

Always on

The work happens whether you open the app or not.

Agents run on schedules, not on prompts. By the time you are awake the overnight feeds have landed, the briefing is written, and the day already has a shape you can argue with.

  1. 04:30Feeds

    The feeds land

    Sleep and training from your watch, balances and positions from your accounts, news and newsletters from the topics you follow. Each feed writes into the vault under its own identity.

  2. 04:55Chief of Staff

    The day gets a shape

    One to three focus items, chosen from every open loop plus everything the other agents surfaced overnight — sized to the windows you actually have free.

  3. 05:00

    Quiet hours end

    Everything written overnight releases together under one header, rather than buzzing your phone at four in the morning.

  4. 06:10Wellness

    Vitals — and an interrupt

    If the week is going badly for the human, Wellness can override the Chief of Staff's picks and call a recovery day. Escalating to an alert bypasses quiet hours; a briefing never does — that distinction is the whole point.

  5. 08:30Assistant

    Inbox triage

    Mail sorted, replies drafted for your approval, and the handful of genuine follow-ups captured into the vault where the Chief of Staff will find them tomorrow.

  6. 12:30Finance

    Midday glance

    Net worth, movement since yesterday, and anything that does not look like your normal spending — with the evidence, not just the flag.

  7. 16:30Product

    Stall watch

    What has been sitting waiting on a decision from you longer than it should have — the quiet failure mode of running more projects than you can hold in your head.

  8. 21:00

    Quiet hours begin

    Briefings hold until morning. Genuine alerts still come through, because an alert that waits for business hours was never an alert.

40

scheduled ops in a full install

60s

scheduler tick

21–05

quiet hours, your timezone

6

agents per person

Extensions

Everything is an extension — including the agents.

The platform ships a registry, not a fixed feature set. Four kinds of package, installed per person or per group, each declaring up front exactly what it needs before it is allowed to run.

  • agent

    Agent types

    The specialists themselves. Install a Chief of Staff, skip Finance entirely, or add a second Product agent scoped to one side project.

    • chief-of-staff
    • executive-assistant
    • wellness
    • finance
    • product
    • intel
  • persona

    Persona packs

    Name-and-voice overlays. Four packs, forty-two painted portraits, and precisely zero effect on what an agent can reach.

    • norse
    • greek
    • angels
    • atlas
  • feed

    Data feeds

    Scheduled collectors that write into the vault under their own commit identity — wearables, bank and crypto snapshots, search analytics, news.

    • wearables
    • banking
    • crypto
    • news
    • search analytics
  • add-on

    Add-ons

    A duty rather than an agent. Bolt one onto a host agent you already run and it composes into that agent's brief, bringing its own tools with it.

    • delivery liaison
    • on-call rotation

What installing actually looks like

  1. Pick a package from the catalog in the console.
  2. Approve the grants it asks for — the exact vault paths it may read and write, shown before you agree.
  3. Supply anything it declares it needs. A package missing a variable installs disabled and says so, rather than silently half-working.
  4. It is live on the next scheduler tick, about a minute later.

Private beta

Bring your own vault. Meet your entourage.

Entourage is in private beta with a small number of households while the group and billing surfaces land. If you want a team of agents that answers in one thread, keeps its memory in a repository you own, and cannot see past your own walls — get in touch and tell us what you'd point them at first.

By invitation · Telegram + web · your vault, your repository