Egregore

Full Command List

Every slash command available in Egregore

The complete catalog of Egregore slash commands, grouped by the layer they act on: ingestion, reflection, and coordination. For a conceptual overview, see Slash Commands.

Reading this page

Commands marked * work in any Egregore, but are significantly enhanced by managed hosting (coming soon) — team-wide visibility via the knowledge graph, routed notifications, cross-session memory.

Core Loop

Every Egregore session runs on this loop: orient, work, capture, close. These are the commands that drive it — each built to make handoffs, context, and coordination between teammates smooth from the first keystroke.

CommandWhat it's for
/activity *The team's situational awareness in one screen — what shipped, what's open, who's asking what. The antidote to standups.
/handoff *Make a session portable. The atomic unit of collaboration: here's what I did, here's what's next, pick it up.
/view *Render any memory artifact — quest, handoff, meeting, decision — as an HTML page you can share via URL.
/quest *Start an exploration others can contribute to over weeks. Larger than a task, smaller than a project.
/invite *Bring someone in — GitHub invite, Egregore setup link, and graph onboarding in one step.
/wrapA personal closing ritual. Turns a drifting session into a captured one.
/save *The one button for "I'm done for now." Commit, push, PR across every repo with changes — the git tax, paid automatically.
/todo *Personal tasks that outlive the session. Hosted: visible to teammates as signal.
/dashboard *Your orientation when you return — what you were last on, what's waiting, where to start.

Reflection

Reflection agents reason with the accumulated context — surfacing what's already known, what's missing, and what's worth promoting into shared memory. This is where Egregore earns its name.

CommandWhat it's for
/reflect *Capture something share-ready — a decision, a pattern, a realization worth keeping. Goes into team memory.
/deep-reflect *A deep-research agent that reasons reflectively across the knowledge base. Multi-sample reasoning over real artifacts — surfaces convergence, tension, gaps, and emergence you'd miss reading one file at a time.

Ingestion

Agents that turn outside context — conversations, meetings, documents — into structured memory.

CommandWhat it's for
/ingest *Unified router for turning outside content into structured memory. Dispatches to the right pipeline based on what you feed it (user interview, transcript, article, dataset).
/meeting *Turn a Granola recording into structured memory — decisions extracted, actions linked to the right people.
/add *Bring an external document, link, or artifact into shared memory.
/archivePreserve a prompt pattern that worked. Future sessions inherit your craft.
/noteA half-baked thought — saved locally and gitignored, never pushed. Stays yours unless you promote it.

Coordination

Multiplayer AI use opens possibilities beyond solo use. These commands handle the communication layer — asking, elicitation, broadcast, and the occasional cleanup.

CommandWhat it's for
/ask *Send a question to a person, the team, or yourself-later. Routed through Telegram in hosted mode.
/harvest *Directed elicitation from a person — extract, deepen, synthesize. The long-form counterpart to /ask.
/announce *Broadcast to the whole group — deliberate, previewed, not impulsive.
/issueReport something broken. Routes to the right tracker.
/delete-user *Remove a member cleanly across access, memberships, and graph.

Identity

CommandWhat it's for
/meTell Egregore what to call you. Your name shows up everywhere your work does.

Git

Egregore automatically enforces safe, cohesive git workflows with hooks and commands that streamline collaboration. /save covers the common path; the rest are here when you need finer control.

CommandWhat it's for
/save *Commit, push, PR across every repo with changes. The command you'll reach for most.
/commitStage and commit changes in the current repo without pushing.
/pushPush the current branch to remote.
/branchCreate a working branch. Usually automatic on your first work-related message.
/prOpen a pull request for the current branch.
/testValidate changes before /save — the pre-flight check.
/review-prCTO-grade review of a PR. Use this on vibe-coded changes before merging.
/contributeSend an improvement back to the upstream Egregore framework. Local patches don't survive /update.

Infrastructure

Configure and maintain your Egregore environment.

CommandWhat it's for
/setupFirst-time Egregore setup.
/tutorialInteractive walkthrough of the core loop.
/checkupDiagnose a broken environment.
/updateSync framework from upstream. Run this when something feels stale.
/pullFetch latest for the current repo and shared memory.
/sync-reposSmart refresh across every managed repo.
/envConfigure environment variables.
/telemetryView or change what Egregore reports back.
/telegram-connect *Wire up Telegram as your notification center.

Build your own

Egregore is a seed — it grows into the organic workflows of the organizations it lives inside. When you notice a pattern worth keeping, capture it as a skill or slash command. /contribute opens a PR against the upstream framework.

On this page