Location: Settings → Preconfigs

A preconfig defines what your agent can do and how it behaves. Each preconfig bundles a system prompt, a set of tools, a default model, and spawn rules for subagents. You can create multiple preconfigs for different tasks and switch between them in any session.

You define the magic

Jean2 ships with a bare minimum default preconfig. There are no opinionated agents, no pre-written personas, no magic out of the box. What you get is a blank canvas.

The experience is entirely what you make it. Write a one-line system prompt and you'll have a basic chatbot. Take the time to craft a detailed system prompt, pick the right tools, enable capabilities, and promote it to an agent, and you'll have something that feels magical.

How good your agent is comes down to how much you push it. And not just the initial setup. You teach it how to learn. You tell it what's worth remembering, when to create a skill, when to search past sessions, when to delegate to a subagent. The capabilities are there, but the agent won't use them well unless you guide it.

The platform gives you the building blocks. You make them sing.

The preconfig list

Set one as default and it will be auto-selected when you open a new session. Other preconfigs are available via the preconfig selector in the chat input.

Edit a preconfig

Click a preconfig to open the editor:

Field	What it does
Name	Display name for the selector
Description	What this agent does. Other agents read this when deciding which subagent to spawn.
Model	Leave unset to inherit the session model
Default	Auto-select this preconfig for new sessions
Tools	Which tools this agent can use. Only granted tools are available.
Temperature	Controls creativity. 0 = deterministic, higher = more random.
Skills	Leave empty to use all available skills, or pick specific ones.
System Prompt	The agent's behavior, role, and constraints. This is where you define what the agent actually does.

Subagent rules

Toggle whether the agent can spawn subagents. If enabled, you can limit which preconfigs it's allowed to spawn, or let it use all of them.

When a subagent is spawned, it runs in an isolated session within the same workspace. Interrupts cascade. Stop the parent, stop them all.

Promote to agent

Any preconfig can be promoted to an agent. This gives it a persistent home: a private workspace, personal memory files, and a skills directory that travel across every project the agent works in.

Promoted agents get two layers of every capability: a workspace-scoped version and a personal one. Memory, skills, and session search all work at both levels. The agent knows the difference and saves accordingly.

See Agents for the full concept.

What's next

Agents: promoted preconfigs with persistent memory, skills, and home workspace
Subagents: how the orchestration works
Chat Controls: switching preconfigs in a session
Skills: SKILL.md instruction sets