Skip to content
Other

Reading Armbrain's Presence Signals

How to tell, at a glance, that Armbrain is actively working — and how to read the signals it embeds in every conversation.

Why This Matters

Claude Desktop looks the same whether Armbrain is running or not. There is no status bar, no pulsing icon, no "logged in" indicator. That made early beta testers ask a reasonable question: "Is this thing even on?"

It is on. You just have to know where to look. Four signals tell you what Armbrain is doing, which client you are in, and how much history it pulled. Once you know the pattern, you will stop wondering — you will be reading the conversation.

Signal 1: The Arrival Greeting

Where you see it: Right after you say "switch to Acme" or any client name.

What it looks like:

Stepped into Acme Corp's Mind. 247 memories from 12 meetings, 3 documents,
and 45 email threads. Since last session: 2 new emails ingested.
Heads up: meeting with Sarah in 2 days, rebrand rock hasn't been updated in 9 days.

How to read it:

For empty client minds, you get a different greeting:

Stepped into Acme Corp's Mind. This mind is empty. Start by telling me about
this client, uploading a document, or ingesting a meeting transcript.
I'll remember everything.

That is the signal to start seeding the client mind.

Signal 2: Memory Provenance

Where you see it: Every time you search memory or Armbrain surfaces something from the past.

What it looks like:

"Derek mentioned the Q3 budget concern and pushed back on the paid
social allocation."
(From meeting transcript, Jan 15)

"Brand positioning centers on 'adventure lifestyle' -- avoid corporate language"
(From uploaded document, Mar 3)

How to read it:

Why this is the most important signal: Claude cannot paraphrase this away. The provenance is the content. That is the one attribution that survives every response.

Signal 3: The Quantification Footer

Where you see it: At the bottom of high-value outputs — meeting prep, weekly summaries, cross-client briefings, document synthesis, campaign reviews.

What it looks like:

---
This briefing drew from 14 memories across 3 months of client history.

How to read it:

Use this to calibrate trust. A meeting prep built from 14 memories across 3 months is a different artifact from one built from 2 memories in the last week. Both are legitimate. You should know which you are reading.

Signal 4: The Onboarding Footer (first 30 days only)

Where you see it: At the bottom of tool responses, but only during your first month.

What it looks like:

_Mind: Acme Corp | 247 memories_

How to read it:

The Correction Moment

There is a fifth behavior that does not show up as a visible marker. When your client's stored memories contradict what generic marketing advice would say, Armbrain is prompted to call that out explicitly. For example:

"Based on this client's Client Mind, their audience skews 45+ and responds to case studies over testimonials — generic advice would miss this."

This is the highest-value moment in the whole system. It is the sentence that proves the difference between "Claude with context" and "Claude without context." It will not fire on every response — Claude sometimes follows the hint, sometimes does not. When it does fire, screenshot it. That is the story you tell a prospect.

What the Signals Tell You Collectively

Put together, these four signals answer four questions you would otherwise have to ask:

QuestionSignal
Am I in the right Client Mind?Arrival greeting
Is this a real memory or a guess?Provenance
How deep is this answer?Quantification footer
Is Armbrain on at all?Onboarding footer (first 30 days)

Once you can read them, you stop asking. The conversation tells you.

When Signals Are Missing

If you switch_client and do not see the greeting, Armbrain did not actually switch. Try again with the exact client mind name.

If a search result has no provenance, something is wrong with the memory record. Report it — that is a bug.

If a meeting prep has no quantification footer, check that you are in a client Client Mind. Personal-client mind outputs and certain administrative calls do not get the footer.

Related Guides