Connect your first tool.
Four short steps: create your free account, paste one MCP URL, add the custom instructions, and try your first prompt. It works the same on mobile and desktop. Your first 7 days are full Pro, free, no credit card and no tokens.
Step 1: Create your free account
Connecting a tool needs a Vilix account. If you haven't already, create your account (opens in a new tab), it's free for 7 days, no credit card. Then come back here and keep going.
Step 2: Connect your tool
OpenClaw runs as a headless agent on a box, with no browser for OAuth. It connects with two things, no demo needed:
https://api.vilix.ai/mcpNo browser OAuth. Generate the key on the Agents page in your Vilix dashboard, then set it as the MCP server's Authorization: Bearer header.
Step 3: Add custom instructions
OptionalTell OpenClaw to actually use Vilix on every message, not just list the tools. This is what turns memory on by default.
I want you to use Vilix MCP as the mandatory memory layer for every message I send unless I explicitly ask for stateless mode.
For EVERY message I send, always follow this exact order:
1. Call:
get_context(user_prompt=<my latest message>)
2. Use the returned context:
- recent_messages
- user_memories
- related_conversations
- instruction
3. Generate your final response internally. Do NOT send it yet.
4. Before replying to me, call:
save_turn(
user_message=<my latest message>,
assistant_message=<exact final response>,
source=<agent/app name>,
chat_id=<existing chat_id if available>
)
5. Return the exact same saved response to me.
STRICT RULES
- Always follow: get_context -> generate_answer -> save_turn -> return_answer
- Apply this to EVERY message I send.
- Never answer before get_context, and never return an answer before save_turn.
- The saved response MUST exactly match the final returned response.
- Reuse chat_id for the same conversation.
If Vilix/MCP tools are unavailable or broken, tell me instead of silently continuing, and ask whether I want to proceed without memory.Step 4: You're all set
Vilix is connected and remembering. Hand your AI its first memory, try these in the tool you just connected:
- Give it something to remember
Seed your memory with what you are working on right now.
Save this to memory: I'm working on [your project] with [your stack]. Keep it in mind in every chat. - Watch it recall
Ask the same tool what Vilix already knows about you.
What do you remember about me and my projects so far? - Now switch tools
Open a different AI tool connected to the same account and pick up the thread. This is the moment Vilix exists for.
Where did we leave off? Continue from my latest context.
Want a dashboard view of what's been saved? Sign in at app.vilix.ai. Stuck? Check the docs or email support@vilix.ai.
Works across your AI tools
- OpenClaw
- Hermes
- Claude Code
- Cursor
- Codex
- ChatGPT
- Claude
- Grok
- Manus AI
- GitHub Copilot
- Windsurf
- Lovable
- Any MCP-compatible AI
- Desktop
- Mobile (same account, same memory)
- Browser & cloud tools
Connect once, and your memory is available everywhere.
Running a headless agent like Hermes or OpenClaw on a box, with no browser for OAuth? It connects with two things:
- 1.The Vilix MCP URL,
https://api.vilix.ai/mcp. - 2.An API key sent as a
Bearerheader. No browser OAuth.
Generate the key on the Agents page in your Vilix dashboard.
Using a different tool?
All you need is your Vilix MCP URL. Any tool that supports custom MCP servers can connect, the flow is the same: paste the URL, approve once, done.
https://api.vilix.ai/mcpNot sure if your tool supports it? Look for “MCP”, “custom connector”, or “MCP server” in its settings. Tell us what you're using and we'll add a walkthrough.