Agent identity

A Lens Prism agent has a persistent identity made of a small set of markdown documents. These documents are always present in the agent's system prompt, so changing them changes how the agent thinks, talks, and acts. All seven are visible in the web UI Profile tabs and the terminal UI config panel.

The seven documents

Document	Purpose	Who edits it
Soul	Personality, values, voice, and hard boundaries — the agent's constitution.	You (the agent can update it on request)
User	What the agent knows about the person or team it works for.	The agent (keeps it current as it learns)
Memory	A curated long-term summary the agent always keeps in context.	The agent
Vision	The user's longer-term goals for the agent to advance proactively.	You
Agent Guide	The operating manual — how the agent should behave, when to reach out, safety norms, Slack etiquette, coding workflow.	You
Heartbeat	The checks the agent runs on its heartbeat schedule.	You
Bootstrap	First-run onboarding instructions; cleared once setup is done.	The agent (clears it)

The split under "who edits it" is about intent, not a hard lock. Documents that capture your intent (Soul, Vision, Agent Guide, Heartbeat) are yours to shape; documents that capture what the agent learns (User, Memory) it maintains itself. In practice you shape all of them through conversation — you ask the agent to change its soul or add a heartbeat check, and it uses its self-management tools to rewrite the document.

Editing the documents

The documents change two ways:

• Through conversation. Tell the agent what you want — "from now on, be more concise," "remember that our staging cluster is eu-west-1," "add a heartbeat check for failing pods." It edits the relevant document itself.

The web UI and TUI panels show these documents as read-only viewers.

The bootstrap flow

On a brand-new agent, the Bootstrap document contains a short onboarding script. The agent uses it to ask who you are, what you want it to focus on, and how you like to work, then writes your answers into its Soul and User documents and calls its clear-bootstrap tool. After that, the Bootstrap tab is empty and the agent operates from its personalized identity. You see this once per agent.

Settings stored on the agent

Beyond the documents, a few dials shape behavior and are stored on the agent:

• Timezone (default UTC) — used for scheduling and daily resets.
• Heartbeat interval (default 8 hours) — see Heartbeat.
• Model — the LLM the agent runs on (defaults to the runtime's configured model).

Adjust these by asking the agent, or from the web UI and TUI where exposed.