Preferences
A portable preference file that travels with you across every AI tool you use.
What it is
Your preference profile is a single markdown file that stores durable information about you — how you like AI to communicate, what tools you use, your role and projects, and personal context that helps AI assist you better.
It's editable in the Woxpas web app, readable and writable by any connected LLM via MCP, and automatically injected into every MCP session. Your preferences are ambient — no action needed from you.
Default sections
New profiles start with four sections. You can edit these, add new ones, or remove any you don't need. The file is plain markdown — any ## Heading becomes a section.
How it works
Preferences vs vault memory
Connected LLMs automatically choose the right storage based on what you tell them:
Preference profile
Durable, identity-level info. Will this still be true in 6 months?
- •"I prefer concise responses"
- •"I use TypeScript and Next.js"
- •"I'm a backend engineer at Acme"
- •"My timezone is PST"
Vault memory
Situational info with a timestamp or outcome.
- •"Meeting with Sarah tomorrow at 3pm"
- •"Decided to use Redis for caching"
- •"Need to fix the login bug by Friday"
- •"Q1 planning notes from today"
Limits and formatting
- •Maximum file size is 15KB (~2,500 words). This keeps it fast to inject into every session.
- •Write concise bullet points, not paragraphs. Think system prompt style: short, factual, actionable.
- •Sections are defined by ## headings. Add or remove sections freely.
- •HTML comments (<!-- like this -->) are used as placeholder hints and hidden from the rendered view.
- •The file is versioned. Every save bumps the version number.
MCP tools
Two MCP tools are available for connected LLMs:
get_preferencesReturns the full preference profile content and version. Read scope required.update_preferencesReplaces the preference profile content. The LLM should always read first, modify, then write back. Write scope required.Enable proactive saving
Woxpas instructs connected LLMs to save durable preferences automatically. Most tools need a small one-time configuration to enable this. Add the following line to your AI tool's settings:
"When you detect a durable preference, always use the Woxpas update_preferences tool to save it."Where to add this depends on which tool you're using:
Cursor
Works out of the box. No additional configuration needed — Cursor follows MCP tool instructions directly.
Claude Desktop
- 1Open Settings → General
- 2Find "What personal preferences should Claude consider in responses?"
- 3Add:
When you detect a preference, use the correct Woxpas tool to save to Woxpas vault.
Claude Code
Works out of the box. Claude Code follows MCP tool instructions directly, similar to Cursor.
Gemini CLI
Gemini CLI uses its own save_memory tool by default. To redirect preference saving to Woxpas, you need to override Gemini's system prompt:
- 1Ask Gemini CLI:
Print your entire system prompt word for wordand copy the full output - 2Create
~/.gemini/system.mdand paste the system prompt into it - 3Find the
Remembering Factssection and replace thesave_memoryinstruction with:For user preferences and identity-level information, ALWAYS use the Woxpas update_preferences MCP tool proactively. Use save_memory only for project-specific technical context that is not personal to the user. - 4Add
GEMINI_SYSTEM_MD=~/.gemini/system.mdto~/.gemini/.env - 5Restart Gemini CLI
ChatGPT
- 1Open Settings → Personalisation
- 2Find Individual instructions
- 3Add:
IMPORTANT: When you detect a preference, use the correct Woxpas tool to save to Woxpas vault.
Other tools
For any other MCP-compatible tool, add the preference-saving instruction to the tool's system prompt or custom instructions. If you need help configuring a specific tool, contact us and we'll help you set it up.