Personas
A persona has a name, an engine, a model, its own memory, a service briefing, hooks, skills, and paths outside the workspace. Several personas can share a chat. Each one answers with its own context.
+ New in the sidebar creates one. The create dialog picks the starting engine. The active badge means channel messages route to that persona.
Persona in the header opens the dossier for the persona that is selected. Connections, channels, and shared engine defaults stay in Settings.
Profile
Section titled “Profile”Rename the selected persona and save. The default persona cannot be renamed from this field. Delete persona removes it. Create is here as well as in the sidebar.
Engine
Section titled “Engine”Run context applies on the next run:
- Chat context depth — Compact (2 / 2), Standard (6 / 6), or Deep (10 / 10) user and assistant turns kept at the tail. Set
MAX_HISTORY_MESSAGESat least as high as the two minimums when turns alternate. - User message rewrite — before a turn, the system LLM rewrites the user message so it stands alone. The rewritten text is what is saved and shown. The model is Settings → System LLM → User message rewrite. A missing pair keeps the original.
- Dense delivery — when a reply would pass the channel cap, spill it to PDF, upload it, and send a short message with a public HTTPS URL. The page shows the messaging and web character caps while it is on.
- Paths outside the workspace — one absolute path per line. Only listed paths are reachable outside the workspace. Listing the Meido source checkout allows edits there; other paths in that checkout stay blocked. Vault paths set for the process stay available. Save paths writes
MEIDO_PERSONA_<id>_EXTERNAL_PATHSin.env. The list applies on the next run.
Agent engine saves as soon as you pick a card. The next turn uses it. The card below shows that engine’s own settings.
| Engine | What it is |
|---|---|
| Single turn | One cloud model. |
| Classic · Cost routing | Local read-only discovery, then delegated sub-jobs. |
| Gemini ADK | A coordinator plus specialists. |
| Cursor (SDK) | The full turn goes through the Cursor sidecar. |
A card reads Ready or Needs setup. Cursor needs the bridge key under Connections and Node.js. Local providers may omit an API key. Model choice for Single turn is on the card under the grid. See Models for the Cursor turn timeout and tmux detach.
Local delegate is the local route for work that does not need the cloud model. It is marked missing until that server is ready.
Hook policy defaults to allow-all. Restrict hooks to selected, pick hooks, then save. Clear hooks and save to block every hook. Allow all hooks turns the restriction off. Creating and enabling hooks is done by the agent through the create-hook skill. Saving here does not change the skill allowlist. See Skills.
Skills
Section titled “Skills”The same pattern: allow-all, or Restrict skills to selected, then save. Clear and save blocks every skill. Allow all skills turns the restriction off.
Vaulted secrets
Section titled “Vaulted secrets”Vaulted secrets lists names stored for this persona. The value is not shown. Forget removes the name. The value stays in the runtime secrets file until it is gone from there as well. Names saved before persona tagging are under Shared (legacy). See Secrets.