Jarvis

A clone of Anthony, living in Slack — the "manager clone" bot model

● Live now Owner-triggered today Runs on Anthony's Mac

Identity

Slack name "Anthony's AI Assistant"

Bot ID U0AE8UF4J23

Model manager clone (1 owner)

Purpose

Phone-to-Claude pipeline plus a queryable clone of Anthony. Send an article, idea, or question. It researches, acts, and replies in-thread.

Brain & memory

Model Claude Opus (1M context)

Account Anthony's Claude subscription

Memory per-thread, 24h

How it runs

Host Anthony's Mac (launchd)

Cadence polls Slack every 15 sec

Batching msgs within 90s = 1 reply

Where it listens & what triggers it

4 dedicated channels

#claude-ant · cst · hr · finance

→ any message triggers it (no mention)

Every other channel / DM

anywhere the bot is invited

→ triggers on @Jarvis or "jarvis"

Net: anywhere Jarvis is added, a tag works — but today it only answers Anthony's tags.

The access wall — what each person can reach

Two locks, kept separate: who may talk to it, and what it may reach.

Anthony (owner) → the full clone

Everything: all work + all personal (health, family, personal finances, non-Emazing projects).

Any other employee → general work only

Project status, processes, department knowledge, web research.

Owner-only, never to teammates

Personal life · Anthony's email · Paycor · QuickBooks · and manager-confidential work: terminations, salaries, peer feedback, things people confide in him.

How a teammate gets access (the gates)

  1. Closed by default. Only Anthony today.
  2. Co-tag to grant. Anthony tags Jarvis + an employee together → it helps that person, that thread, that topic. No standing access.
  3. Ask-me-first for anyone else. An employee pings it uninvited → it stays silent to them and DMs Anthony for the ok.
  4. Read-only for teammates. Jarvis answers them but won't act as Anthony (send, file, edit) on their behalf.
  5. Data wall always holds. A granted conversation never unlocks the owner-only list above. A confidential tripwire refuses salary / termination / named-performance questions even in work scope, and every teammate session is logged to a private audit sheet.

Owner's full toolset

Basecamp Google Workspace Google personal Google Sheets Notion Paycor QuickBooks Granola Loop Returns Playwright browser Web + files

Teammate sessions run on a stripped subset of this, per the wall above.

Emazing Group · prepared for the company Slack-bot template comparison · June 10, 2026