Chat Settings configure how the 📝Chat & RAG agent behaves for you and for visitors — system prompts, model selection, who's allowed to chat, spending caps, and rate limits, all in one place. They exist so a creator can shape their agent's personality and guardrails without touching code. They're for any creator running a public-facing chat who wants control over cost, access, and tone.
Key Capabilities
- Separate system prompts — one for your own chat sessions, one for visitors
- Model selection — choose the model for owner chat, visitor chat, or override per visitor tier
- Visitor access controls — turn visitor chat on or off, separately allow or block anonymous and logged-in visitors, and choose whether you are notified of each new visitor chat
- Chat name — the name on your Ask button (Ask followed by the name)
- What chat retrieves — a grid of who is asking against which memo visibilities chat may draw on; it can only narrow what a visitor could already read
- Summaries — optional rolling summaries of visitor conversations on your Activity timeline, with a model you choose
- Budget caps — set monthly, anonymous, and authenticated spending caps in dollars
- Rate limits — override the platform's default per-hour limits for anonymous visitors, logged-in visitors, and contacts; turn a group off to block it (anonymous, logged-in) or make it unlimited (contacts)
Getting Started
- Go to Settings → Chat
- Write separate system prompts for your own sessions and for visitors
- Set visitor access, budget caps, and rate limits as needed
FAQ
- What does "anonymity" control here? Whether logged-out visitors can chat at all — it's a visitor-access toggle, not a creator-identity feature.
- What happens if a budget cap is hit? Chat requests are blocked with a clear error until the cap resets or is raised.
- Do rate limits apply to me, the owner? No — the library owner's own requests bypass rate limiting entirely.
- What are the default rate limits if I don't set my own? 10 requests/hour for anonymous visitors and 100/hour for authenticated visitors, platform-wide defaults you can override per library.