@rubytech/create-realagent 1.0.406

package/payload/platform/plugins/deep-research/skills/deep-research/references/search-strategy.md

@@ -0,0 +1,24 @@
+# Search Strategy and Source Evaluation
+
+## Query Crafting (Phase 2)
+
+Map each sub-question to one or more targeted search queries:
+
+- Keep queries short (3–6 words). Specific nouns beat vague phrases.
+- Vary query framing: try the direct question, a "site:domain" form, and a comparison form where relevant.
+- For competitive intelligence: always search the target company directly AND search for independent reviews/comparisons.
+- For literature/academic queries: search for primary papers, then for secondary summaries.
+- For fast-changing topics (pricing, funding, personnel): append the current year to queries.
+- Never repeat the same query twice. If a search returns poor results, rephrase — don't retry identical terms.
+
+## Source Fetching and Extraction (Phase 3)
+
+For each source returned:
+
+1. Fetch the full page content where possible, not just the snippet.
+2. Extract only what is relevant to the sub-question that drove this search.
+3. Note the publication date if visible.
+4. Flag sources older than 18 months as `[possibly outdated]`.
+5. Prefer: official docs, primary research, reputable press. Deprioritise: forums, SEO farms, undated pages.
+
+Do not quote large blocks verbatim. Paraphrase and extract the key claim or data point.

package/payload/platform/plugins/docs/PLUGIN.md

@@ -0,0 +1,44 @@
+---
+name: docs
+description: "Comprehensive user guide and platform documentation for Maxy. Load references when users ask how-to, setup, or troubleshooting questions. Also contains platform architecture references for admin use."
+metadata: {"taskmaster":{"always":true,"embed":["public","admin"],"emoji":"📖","pluginKey":"docs"}}
+---
+
+# Maxy Documentation
+
+This plugin is the single source of truth for Maxy documentation. It ships with every install and is always the version the user has installed.
+
+Load the relevant reference when the user asks a how-to question, requests help with setup, reports an issue, or wants to understand how something works.
+
+## User Guide
+
+Load these when users ask about Maxy features or need guidance:
+
+- **Getting started** → `references/getting-started.md` — first run, what Maxy is, how to use it
+- **Plugins** → `references/plugins-guide.md` — what plugins are, how to install/remove them, the marketplace
+- **Memory** → `references/memory-guide.md` — how Maxy remembers things, what is stored, privacy
+- **Contacts** → `references/contacts-guide.md` — adding, looking up, and managing contacts
+- **Telegram** → `references/telegram-guide.md` — Telegram setup, the bot, daily use
+- **Settings** → `references/settings.md` — output style, effort level, context mode, account preferences
+- **Access Control** → `references/access-control.md` — who can chat with your public agent, invitations, authentication
+- **Troubleshooting** → `references/troubleshooting.md` — common issues and how to resolve them
+
+## Platform Reference
+
+Load these when performing admin tasks or diagnosing platform behaviour:
+
+- **Platform architecture** → `references/platform.md` — how the platform works, agent types, the plugin model
+- **Deployment** → `references/deployment.md` — Pi setup, Cloudflare tunnel, start script
+
+## References
+
+- references/getting-started.md
+- references/plugins-guide.md
+- references/memory-guide.md
+- references/contacts-guide.md
+- references/telegram-guide.md
+- references/settings.md
+- references/access-control.md
+- references/troubleshooting.md
+- references/platform.md
+- references/deployment.md

package/payload/platform/plugins/docs/references/access-control.md

@@ -0,0 +1,51 @@
+# Access Control
+
+## What It Is
+
+Access control determines who can chat with your public agent. By default, anyone with your public URL can start a conversation. You can restrict this so only invited people have access.
+
+## Access Modes
+
+Each public agent has one of three access modes:
+
+| Mode | Who can chat |
+|------|-------------|
+| Open (default) | Anyone with the URL. No login required. |
+| Gated | Invitation only. Visitors must be invited by you and authenticate before the chat loads. |
+| Paid | Same as gated — visitors must be invited and authenticated. The label distinguishes paying clients from free invitees, for your own tracking. |
+
+Gated and paid work identically — the difference is a label for your records. Both require visitors to authenticate before they can see the chat.
+
+## How to Set It Up
+
+Tell Maxy: "Set my public agent to gated access" or "Make the coaching agent invitation-only."
+
+Maxy changes the access mode. The next visitor to your public URL will see a login screen instead of the chat.
+
+## Inviting Visitors
+
+Tell Maxy who to invite: "Invite sarah@client.co to the coaching agent" or "Give Tom access to my public agent — his number is 07700 900123."
+
+Maxy creates an invitation and sends a magic link (email) or OTP (phone). The visitor clicks the link, sets a password, and gains access.
+
+## What Visitors Experience
+
+- **First visit (invited):** The visitor receives an email or message with a link. Clicking it takes them to your public URL where they set a password. After that, they're in the chat.
+- **Return visits:** The visitor enters their email/phone and password to log in.
+- **Expired access:** If their access period has passed, they see an expiry message with the date.
+- **No invitation:** If someone reaches a gated URL without an invitation, they see a login screen with a note that access requires an invitation.
+
+## Managing Access
+
+All access management is done through conversation with Maxy:
+
+- "Who has access to my coaching agent?" — lists active visitors
+- "Revoke Sarah's access" — permanently deactivates her access
+- "Extend Tom's access by 30 days" — pushes the expiry date forward
+- "Set all access to expire after 90 days" — applies a default expiry to new invitations
+
+Revoked access is permanent — the visitor cannot log in again unless re-invited.
+
+## Visitor Identity
+
+When a visitor is authenticated, your public agent knows their name and contact details. It can personalise responses ("Welcome back, Sarah") without needing to ask.

package/payload/platform/plugins/docs/references/contacts-guide.md

@@ -0,0 +1,59 @@
+# Contacts Guide
+
+## What a Contact Is
+
+A contact is a Person node in Maxy's memory graph. Each person has a first name and email address, plus optional fields like last name, phone number, and job title. Contacts are linked to conversations, other people, and business context.
+
+## Adding a Contact
+
+Tell Maxy naturally:
+
+- "Add John Smith to my contacts — he's a potential client I met at the conference"
+- "Create a contact for sarah@acme.com, her name is Sarah Chen, she's the head of procurement at Acme"
+
+Maxy will extract the details and confirm the record before saving.
+
+Required: first name and email address. Everything else is optional but useful.
+
+## Looking Up a Contact
+
+Ask naturally:
+
+- "What do you know about John Smith?"
+- "Look up Sarah Chen"
+- "Find the contact from Acme procurement"
+
+Maxy searches by name, company, email, or any detail you provide.
+
+## Updating a Contact
+
+Tell Maxy what changed:
+
+- "Update John Smith's email to john@newcompany.com"
+- "Add a note to Sarah Chen's record: prefers evening calls"
+- "John Smith is now at Horizon Capital, not Acme"
+
+## Listing Contacts
+
+- "List all my contacts"
+- "Show me everyone from Acme"
+- "Who are my contacts in fintech?"
+
+## The Waitlist
+
+For businesses using Maxy's public agent: when a visitor expresses interest in signing up, the public agent collects their name and email in conversation. The waitlist plugin's scheduled extraction job processes these conversations and creates Person nodes with status `waitlist`.
+
+To review the waitlist: "Show me the waitlist" or "Who's on the waitlist?"
+
+## Stored Fields
+
+| Field | Description |
+|-------|-------------|
+| `givenName` | First name (required) |
+| `familyName` | Last name (optional) |
+| `email` | Email address (required — used to deduplicate contacts) |
+| `telephone` | Phone number |
+| `jobTitle` | Job title or role |
+| `source` | Where this contact came from (e.g. "public.maxy.bot", "telegram", "manual") |
+| `status` | Contact status (e.g. "active", "prospect", "waitlist") |
+| `createdOn` | When the record was created |

package/payload/platform/plugins/docs/references/deployment.md

@@ -0,0 +1,71 @@
+# Deployment Guide
+
+## Hardware Requirements
+
+- Raspberry Pi 5 (16GB RAM minimum)
+- 256GB storage (microSD or NVMe)
+- Raspberry Pi OS
+- Always-on power and network connection
+
+## Initial Setup
+
+The Maxy installer handles the full setup. Run it on your Pi:
+
+```bash
+npx -y @rubytech/create-maxy
+```
+
+This installs all dependencies (Node.js, Neo4j, Cloudflare tunnel, Claude Code), configures the platform, and starts all services.
+
+## What the Installer Does
+
+1. Installs system dependencies
+2. Installs Claude Code (the AI engine) and configures it
+3. Installs and starts Neo4j (the memory database)
+4. Installs and configures the Cloudflare tunnel for remote access
+5. Creates your account and sets your PIN
+6. Starts the Maxy web server on port 19200
+7. Configures systemd so everything restarts automatically if the Pi reboots
+
+## Service Management
+
+Maxy runs via systemd and starts automatically on boot. You don't need to start it manually. To check if it's running, ask Maxy "Check system status."
+
+If you need to restart the service manually (rare), ask Maxy to do it for you.
+
+## Remote Access via Cloudflare
+
+Maxy uses a Cloudflare tunnel to make your local Pi accessible from anywhere without opening router ports. The tunnel is configured during setup and runs as a background service.
+
+Your public URL looks like: `https://your-name.maxy.chat` (or a custom domain you configure).
+
+To check the tunnel status: ask Maxy "Check Cloudflare tunnel status."
+
+To restart the tunnel: ask Maxy "Restart the Cloudflare tunnel."
+
+## Checking Service Status
+
+Ask Maxy: "Check system status."
+
+The `system-status` tool reports the health of all services: Neo4j, the web server, the Cloudflare tunnel, and all active MCP servers.
+
+## If Maxy Won't Start
+
+From the Pi directly:
+
+```bash
+sudo systemctl status maxy
+sudo journalctl -u maxy -n 50
+```
+
+The logs will show which service failed to start and why. Common causes:
+
+- **Neo4j not started** — run `sudo systemctl start neo4j` and retry
+- **Port 19200 already in use** — check for another process: `lsof -i :19200`
+- **Claude OAuth expired** — the next admin session will prompt you to re-authenticate
+
+## Upgrading
+
+To upgrade Maxy to the latest version, ask Maxy: "Upgrade Maxy." The platform will pull the latest version, restart services, and confirm when done.
+
+The docs plugin (this plugin) is upgraded in the same step — you always have the documentation that matches your installed version.

package/payload/platform/plugins/docs/references/getting-started.md

@@ -0,0 +1,45 @@
+# Getting Started with Maxy
+
+## What Maxy Is
+
+Maxy is a personal and business AI assistant that runs on a Raspberry Pi in your home. It connects to your services — Telegram, your contacts, your calendar — and acts as a proactive agent. It remembers context across conversations and takes action on your behalf.
+
+Because Maxy runs locally, your data stays in your home. It never passes through someone else's cloud.
+
+## The Two Interfaces
+
+**Admin (you)** — accessed at your local address (e.g. `maxy.local:19200`) or remotely via your Cloudflare domain. The admin interface is protected by a PIN. This is where you manage Maxy: configure settings, manage contacts, review activity, and have full conversations. The admin agent has access to all your plugins and can take action.
+
+**Public (visitors)** — anyone who reaches your public URL gets the public agent. It handles product enquiries, collects waitlist signups, and answers questions about your business. It cannot read or write your private data.
+
+## First Run
+
+When you first open the admin interface:
+
+1. Set your PIN — this protects access to the admin interface
+2. Connect to Claude — Maxy will guide you through connecting to your Claude account
+3. Enter your PIN to log in
+4. Maxy walks you through onboarding: choosing which plugins to activate, setting up remote access, and configuring your account
+
+This setup is resumable — if you close the browser mid-setup, Maxy picks up where you left off next time.
+
+## How to Use Maxy
+
+Conversation is the only interface. Type what you need:
+
+- "Add John Smith to my contacts, he's a potential client from the conference"
+- "Schedule a call with Sarah for Thursday at 2pm"
+- "What did I last discuss with Tom?"
+- "Send a Telegram message to the team: standup in 10 minutes"
+
+Maxy understands plain language. You don't need to learn commands or navigate menus.
+
+## What Maxy Remembers
+
+Maxy maintains a memory graph of everything important: contacts, conversations, preferences, relationships, and context. When you tell Maxy something, it stores it. When you ask about something later, it retrieves it.
+
+You can always tell Maxy to remember or forget specific things: "Remember that I prefer morning calls" or "Forget what I said about the Johnson account."
+
+## Getting Help
+
+Ask Maxy anything. If you want to know what it can do, just ask: "What can you help me with?" or "How do I set up Telegram?"

package/payload/platform/plugins/docs/references/memory-guide.md

@@ -0,0 +1,87 @@
+# Memory Guide
+
+## How Memory Works
+
+Maxy maintains a graph of everything you've told it. Contacts, conversations, preferences, relationships, business context — all stored as connected nodes in a local Neo4j database on your Raspberry Pi.
+
+When you ask Maxy about something, it searches this graph first. It retrieves relevant context before responding, which is why Maxy can pick up where you left off even across separate sessions.
+
+The graph lives entirely on your hardware. Nothing is sent to the cloud.
+
+## What Gets Remembered
+
+Maxy stores:
+
+- **Contacts** — people, companies, relationships between them
+- **Conversations** — key decisions, commitments, follow-ups mentioned in chat
+- **Preferences** — things you've told Maxy about how you like to work
+- **Context** — project status, ongoing threads, background you've shared
+
+Maxy remembers details you mention naturally: "I'm meeting with Sarah on Thursday" creates a memory that Thursday has a meeting with Sarah.
+
+## Telling Maxy to Remember Something
+
+Just say it naturally:
+
+- "Remember that I prefer morning calls"
+- "Note that the Johnson account is on hold until March"
+- "My wife's name is Emma, keep that in mind"
+
+Maxy will confirm and store it.
+
+## Telling Maxy to Forget Something
+
+Be direct:
+
+- "Forget everything about the Johnson account"
+- "Remove Sarah's contact record"
+- "Clear what you know about my pricing preferences"
+- "Delete that pricing guide I uploaded"
+
+Maxy will confirm before deleting anything significant. Documents are soft-deleted first (excluded from search but recoverable for 7 days). Say "permanently delete" to remove immediately.
+
+## Managing Documents
+
+### Listing files
+
+Ask: "What files do I have stored?" or "List my attachments"
+
+Maxy shows all uploaded files with their ingestion status — whether they've been processed into the knowledge graph.
+
+### Reading files
+
+Ask: "Show me what's in the pricing guide" or "Read the quarterly report"
+
+Maxy returns the full content of text and markdown files, extracted text from PDFs, and metadata for images.
+
+### Editing files
+
+Ask: "Update the pricing in that document" or "Change the introduction paragraph"
+
+Maxy reads the file, makes the edit, and prepares it for re-ingestion into the knowledge graph. Only text and markdown files can be edited — PDFs and images cannot.
+
+### Renaming files
+
+Ask: "Rename that file to quarterly-report-q1.pdf"
+
+Maxy updates the filename in both the stored metadata and the knowledge graph.
+
+### Deleting documents
+
+Ask: "Delete the old pricing guide"
+
+By default, documents are soft-deleted — they stop appearing in search results but remain recoverable for 7 days. To permanently delete immediately, say "permanently delete" or "force delete".
+
+## Searching Memory
+
+Ask naturally:
+
+- "What do you know about Tom Henderson?"
+- "What did I last discuss about the Acme proposal?"
+- "Who have I met from the fintech conference?"
+
+## Privacy
+
+All memory is stored on your local Raspberry Pi. The Neo4j database never leaves your network. Maxy does not sync memory to any cloud service or third party.
+
+If you want to wipe everything and start fresh, ask: "Reset my memory graph." Maxy will ask for confirmation before doing so.

package/payload/platform/plugins/docs/references/platform.md

@@ -0,0 +1,64 @@
+# How Maxy Works
+
+## The Short Version
+
+Maxy runs on a Raspberry Pi in your home. It uses Claude (Anthropic's AI) as its brain and extends it with plugins — modular capabilities like contacts, Telegram, and memory. Everything stays local: your data, your conversations, your memory graph.
+
+## The Raspberry Pi
+
+Maxy is a server that lives on your local network. It's always on, always available, and accessible:
+
+- **Locally:** `maxy.local:19200` (or the IP address of your Pi)
+- **Remotely:** via your personal domain, routed through a Cloudflare tunnel
+
+The Pi runs the web interface, the AI agent, and all the plugin servers. When you send a message, the Pi processes it — not a cloud service.
+
+## The Two Agents
+
+Maxy runs two agents simultaneously:
+
+**Admin agent (you)** — full access to all tools and plugins. This is the agent you interact with at your local or remote URL. It can read and write contacts, send Telegram messages, manage your account, and perform any task you have plugins for. Protected by your PIN.
+
+**Public agent (visitors)** — read-only access. Handles enquiries from people who reach your public URL. It can answer questions about your business and collect waitlist signups, but it cannot access your private data or take actions.
+
+## Plugins
+
+Everything Maxy can do is provided by a plugin. Each plugin is a self-contained package:
+
+- Behaviour instructions (how the agent should act)
+- Tools (specific actions the agent can take, exposed via MCP servers)
+- Reference documents (detailed knowledge loaded on demand)
+
+Plugins are installed and managed through conversation. You can add marketplace plugins (Stripe, Zapier) or use Maxy's built-in ones (contacts, memory, Telegram).
+
+## Specialist Subagents
+
+Maxy has specialist helpers it can dispatch for specific tasks. You don't need to configure or manage them — Maxy decides when to use them and handles everything automatically. You may see activity like "Dispatching document-specialist..." in the chat timeline when this happens.
+
+| Specialist | What it does |
+|-----------|-------------|
+| Browser specialist | Automates browser tasks — navigating websites, filling forms, extracting information |
+| Memory specialist | Performs focused memory operations — searching, writing, and reindexing your knowledge graph |
+| Admin specialist | Handles platform administration — Cloudflare tunnel management, Telegram setup, system configuration |
+| Document specialist | Ingests documents and files into your memory graph for searchable storage |
+| Researcher | Conducts web research — searching, fetching content, and storing findings in memory |
+
+Specialists are installed during setup and listed when Maxy introduces itself. Some premium plugins add their own specialists (e.g. the writer-craft plugin adds a manuscript reviewer). Specialists installed mid-session become active from the next session.
+
+## Memory
+
+Maxy maintains a graph database (Neo4j) of everything you've told it. People, conversations, preferences, and context are stored as connected nodes. When you ask Maxy something, it searches this graph to retrieve relevant context before responding.
+
+The memory graph is stored on your Pi. It never leaves your network.
+
+## The Web Interface
+
+The web app runs on your Pi on port 19200. It provides:
+
+- **Admin chat** (at `/`) — your primary interface, PIN-protected
+- **Public chat** (at `/{agent-name}`) — visitor-facing agents, each with their own URL. On public hostnames, the root path serves the default agent.
+- **Telegram bot landing** (at `/bot`)
+
+There is no dashboard, no settings panel, no menus. Everything is done through conversation.
+
+The chat input auto-grows as you type — it expands to fit your message and shrinks back when you delete text. You can also drag the resize handle above the input to set a custom height.

package/payload/platform/plugins/docs/references/plugins-guide.md

@@ -0,0 +1,83 @@
+# Plugins Guide
+
+## What a Plugin Is
+
+A plugin extends what Maxy can do. Each plugin adds a focused capability — contacts management, Telegram messaging, scheduling, email, research. Plugins are modular: you enable only what you need.
+
+Maxy's own capabilities are plugins too. Marketplace plugins (Stripe, Zapier) work the same way — Maxy manages all of them through conversation.
+
+## Plugin Groups
+
+### Core (always active)
+
+These are part of Maxy's foundation and cannot be disabled:
+
+| Plugin | What it does |
+|--------|-------------|
+| `admin` | Platform management — system status, account settings, logs, session control |
+| `memory` | Graph memory — search, write, reindex, and ingest knowledge |
+| `maxy-guide` | User guide and platform documentation (this plugin) |
+| `cloudflare` | Cloudflare Tunnel — remote access via your custom domain |
+| `anthropic` | Claude connection — API key acquisition and configuration |
+
+### Maxy Plugins (user-selectable)
+
+These are enabled during onboarding and can be added or removed at any time:
+
+| Plugin | What it does |
+|--------|-------------|
+| `business-assistant` | Customer enquiries, scheduling, quoting, invoicing, daily briefings |
+| `sales` | Buying signal detection, closing techniques, objection handling |
+| `scheduling` | Calendar and scheduling — events, appointments, recurring triggers |
+| `tasks` | Task lifecycle — create, update, list, relate, complete |
+| `email` | Agent email account — setup, read, send, reply, search, OTP extract, status, auto-respond config |
+| `contacts` | CRM contact management — create, lookup, update, list |
+| `workflows` | Persistent named workflows — reusable instruction sets |
+| `projects` | Structured project execution — phased sprints, investigations, reviews, retrospectives (requires Tasks plugin) |
+| `web` | Web research — search and content fetching |
+| `telegram` | Telegram bot — BotFather setup, messaging, channels |
+| `waitlist` | Waitlist lifecycle — extract sign-ups from conversations, review |
+
+### Claude Official (marketplace)
+
+Third-party plugins from the Claude marketplace:
+
+| Plugin | What it does |
+|--------|-------------|
+| `stripe` | Live access to payment and business data |
+| `zapier` | Cross-app automation — connect thousands of apps |
+
+### Premium Plugins
+
+Premium plugins are one-off purchases that grant permanent ownership. They are not part of the standard install — once purchased, Maxy delivers them automatically.
+
+| Plugin | Type | What it does |
+|--------|------|-------------|
+| `teaching` | Skills | Interactive tutoring, lesson planning, and study pack generation from your knowledge base |
+| `real-agency` | Skills | UK estate agency skills — sales, negotiation, listing presentations, vendor management, buyer handling, and business growth |
+| `writer-craft` | Skills + Agent | Manuscript review and writing craft — story architecture, reader engagement, prose craft, editorial practice, and multi-level review |
+
+**How it works:** When you purchase a premium plugin, it's delivered to your Maxy via conversation. Tell Maxy "Enable the teaching plugin" and it handles the rest. Premium plugins are yours permanently — they survive updates and reinstalls.
+
+Some premium plugins include specialist helpers that Maxy can dispatch for specific tasks (e.g. the writer-craft plugin includes a manuscript reviewer). These are activated automatically when the plugin is enabled.
+
+Some premium plugins ship pre-built workflows that are created when the plugin is enabled. These workflows are fully yours — you can inspect, edit, run, and manage them through conversation, exactly like workflows you create yourself. The plugin provides the starting point; you own the result.
+
+## Choosing Plugins
+
+During first-time setup, Maxy presents a plugin selection screen where you choose which plugins to activate. Core plugins are pre-selected and locked. Recommended plugins are pre-selected but optional. You can change your mind later.
+
+## Adding or Removing Plugins
+
+Tell Maxy:
+
+- "Enable the Telegram plugin"
+- "Add the Stripe plugin"
+- "Disable the waitlist plugin"
+- "Remove Zapier"
+
+Maxy handles the installation or removal. If the plugin requires any setup (API keys, bot tokens, configuration), Maxy will walk you through it.
+
+## Viewing Your Plugins
+
+Ask Maxy: "What plugins do I have?" or "List my plugins."

package/payload/platform/plugins/docs/references/settings.md

@@ -0,0 +1,89 @@
+# Settings
+
+## Output Style
+
+Controls how Maxy communicates with you.
+
+| Style | Behaviour |
+|-------|-----------|
+| `default` | Concise, direct responses — gets to the point |
+| `explanatory` | More detailed responses with educational context — explains reasoning and trade-offs |
+
+**Changing output style:** Tell Maxy "Switch to explanatory mode" or "Use default output style."
+
+Changes take effect on the next session. The current session continues with the existing style.
+
+## Effort Level
+
+Controls how much work Maxy puts into each task — specifically, how many steps it takes before stopping and checking with you.
+
+| Level | Max turns | Use when |
+|-------|-----------|----------|
+| `low` | 5 | Quick questions, simple lookups |
+| `medium` | 10 | Standard tasks — most daily use |
+| `high` | 20 | Complex multi-step tasks |
+| `auto` | 20 | Let Maxy decide (same ceiling as high) |
+| `max` | 40 | Long autonomous workflows |
+
+**Changing effort level:** Tell Maxy "Set effort to high" or "Use low effort mode."
+
+Changes take effect on the next session.
+
+## Thinking View
+
+Controls how Maxy's thinking process is displayed in the chat.
+
+| Mode | Behaviour |
+|------|-----------|
+| `default` | Thinking steps shown expanded, tool use collapsed |
+| `expanded` | Everything shown expanded — thinking, tool use, and results |
+| `collapsed` | Everything collapsed — compact view, expand on tap |
+
+**Changing thinking view:** Tell Maxy "Show thinking by default", "Show everything expanded", or "Hide thinking."
+
+Changes take effect on the next session.
+
+## Viewing Current Settings
+
+Ask Maxy: "What are my current settings?" or "What output style am I using?"
+
+## Context Mode
+
+Controls how Maxy manages conversation history between messages.
+
+| Mode | Behaviour |
+|------|-----------|
+| `claude-code` (default) | Maxy maintains a continuous session across messages. Conversation flows naturally — each message picks up where the last left off. When the session gets long, Maxy automatically summarises and starts fresh so it doesn't lose track. |
+| `managed` | Each message starts a fresh session. Maxy keeps a rolling history of your conversation and injects it into each new session. Older messages are trimmed and saved to memory when the history gets too long. You'll see a usage indicator in the footer showing how much history is being carried. |
+
+Both modes preserve your conversation context — they differ in how that context is stored and carried forward. Most users should keep the default (`claude-code`). Switch to `managed` if you notice Maxy losing context in long sessions or if you prefer the rolling-history approach.
+
+**Changing context mode:** Tell Maxy "Switch to managed mode" or "Use claude-code mode." You can also click the context mode value in the info panel. Changes take effect on the next message.
+
+## Default Agent
+
+Controls which public agent serves the root URL (`/`). Visitors who go to your public site without specifying an agent slug see this agent.
+
+**Changing the default agent:** Tell Maxy "Make sales the default agent" or "Set the default to support."
+
+The change takes effect on the next page load. The previous default agent remains accessible at its `/{slug}` URL.
+
+## Account Preferences
+
+You can ask Maxy to show or change any of the following:
+
+- Default agent (which public agent serves the root URL)
+- Admin model (which Claude model powers the admin agent)
+- Public model (which Claude model powers the public agent)
+- Output style
+- Effort level
+- Context mode
+- Enabled plugins
+
+Tell Maxy what you want to change and it handles the rest.
+
+## PIN
+
+Your admin PIN is set during initial setup. To change it, ask Maxy: "Change my admin PIN."
+
+Maxy will ask for your current PIN to verify, then set the new one.