Ghampus chat — topics, hats & one room
Graphnosis chat is one room, not a stack of disposable AI threads. Ghampus Hush is the orchestrator in that room — your confidential AI who routes conversation, watches memory, and keeps the cortex honest. Specialist agents (Agempi) wear Digital Hats and join when you invite them.
This guide is the product model. For the seahorse etymology, see The story of Ghampus.
The one-room idea
| Idea | What it means |
|---|---|
| One chat surface | You don’t hop between separate agent apps. Everyone speaks in the same Ghampus room. |
| Ghampus orchestrates | Untagged messages go to Ghampus only. He proposes topics, watches memory, and can surface a Save to your cortex? card when something worth keeping appears. |
| Agempi wear Digital Hats | Each Agempus is a specialist persona (avatar, role, skills). Several of them together are Agempi. Hats make who is speaking obvious. |
| Topics are living lanes | Work grows as Topics — durable conversation lanes tied to themes. They are not buried under endless old session noise. |
| Chat Sessions are history | Clearing a topic soft-archives the prior transcript under Chat Sessions. Recoverable history — not the place you live day to day. |
Digital Hats (Agempi)
Open Agents / Agempi in the app. Each tile is an Agempus: name, avatar, optional hat, skills, and an on/off switch.
- Turn an Agempus off → its skills go quiet everywhere (including connected AI clients over MCP).
- Drag tiles into a crew and set one autonomy level for the group.
- In chat, type
@to invite by name, crew, or @everyone (Ghampus ranks who joins — typically a small top set, not the whole roster).
Hats are the visual shorthand for who is answering. The memory of what was said still lands in your cortex only when you (or Ghampus, under your memory policy) save it.
How to talk in the room
- No
@tags — Ghampus answers alone. Good for “what were we drafting?” and orchestrator questions. @Name— that Agempus is primary. You can tag a few names; they stay sticky until you clear the chips.@everyoneor@Crew— Ghampus invites a small ranked set from the room (or the topic’s bound crew).@Ghampus— talk to the orchestrator only; other Agempi stay quiet for that sticky tag.- 1:1 Focus — on an Agempus bubble, tap 1:1 Focus for a DM-like lane in the same room. Mentions are paused while Focus is on; Ghampus still watches for memory saves in the background. Dismiss returns to the open room.
Crew discuss stays on by default: peers join when you @ them (or @everyone / a crew). Empty tags never flood the roster.
Topics vs Chat Sessions
Topics are the lanes you follow:
- Switch topics from the rail / phone drawer (Pins → Topics → Chat Sessions).
- Pin important topics so they float above the rest.
- Ask Ghampus to fork a topic (“let’s talk about launch planning”) — confirm-first for weaker signals; soft auto only for clear explicit forks.
- Clear chat empties the visible thread for that topic and archives the prior transcript. Cortex memory is untouched.
Chat Sessions are recoverable history:
- Cleared or orphaned transcripts appear here.
- Search across sessions from the topic-bar magnifier (This chat | Chat sessions) or by asking Ghampus.
- Pin a session within Chat Sessions if you want it handy — pins of topics stay in the Pins section above.
Day-to-day work lives in Topics. Chat Sessions exist so nothing useful disappears when you clear a thread.
In-chat actions (same window)
Everything below stays in the Ghampus room — no bounce to a separate corrections deck for ordinary saves:
| Action | What it does |
|---|---|
| Remember / Save to cortex | Opens a confirm card (excerpt, suggested engram, privacy tier). You approve before anything writes. |
| Reply | Seeds compose with context from that bubble. |
| Quote | Select text → Quote adds a compact chip above compose. Multi-quote several speakers; send clears the chips. |
| Comment | Select text → Comment to annotate without leaving the thread. |
| 1:1 Focus | Sticky specialist lane; see above. |
Ghampus may also offer a Save to your cortex? card on high-precision corrections (“correct the record”, explicit remember). Approve or dismiss inline.
Voice (when available)
On phone / browser UI with voice enabled: hold the mic to talk, release to send. A short mic tap can reveal language options. Follow-voice and tap-to-hear cover speaking replies back. Desktop mic support may lag the phone path depending on build — the chat actions above work either way.
Mobile and desktop
The same room model ships on desktop and on phone (browser access to your personal server). Layout differs — rail vs drawer, Enter-to-send vs soft-keyboard newlines — but Topics, Pins, Chat Sessions, @ mentions, 1:1 Focus, and Remember live in both places.
See Connect from Your Phone for reaching your cortex remotely.
What stays private
- Engrams use sensitivity tiers: public → deidentified (non-PII) → sensitive. See Graphs & Sensitivity Tiers.
- Sensitive material stays local by default; consent gates apply before cloud paths can see it.
- Agempi may propose remembers; cortex writes go through Ghampus / your explicit approval — not silent specialist writes.
Linked files, Savings, Shares
From the Ghampus-oriented navigation you can also reach:
- Linked files — attach paths without ingesting the whole file into memory.
- Savings — counterfactual cost of recalls that replaced paid LLM context dumps.
- Shares — collaborate on engrams with people you choose (Engram Sharing).
Related
The story of Ghampus — name, seahorse, principles.
Skills as SOPs — what Agempi execute.
Graphs & Sensitivity Tiers — privacy ladder.
Connect from Your Phone — same cortex on mobile.