Operating Modes
term2 provides built-in profiles for different stages of development and system administration.
Operating Profiles
Section titled “Operating Profiles”| Profile | Activation | Purpose | Observable Capabilities & Restrictions |
|---|---|---|---|
| Standard | Default (term2), /profile standard |
Primary engineering mode for everyday development. | Full codebase context, file reading and editing, shell execution, subagents. |
| Bare | --profile bare, /profile bare |
Minimal system prompt baseline while retaining essential quality safeguards and completion verification. | Shell-led codebase work, subagent delegation, read_file for images, project instructions, the skills catalog, and environment context; selected web, memory, session, MCP, and background-task capabilities are available through run_code. |
| Plan | /plan, Shift+Tab, /profile plan |
Architecture design, research, and code review. | Read-only operation: file modifications, file creations, and mutating shell commands are prevented. |
| Lite | term2 --lite, /lite, /profile lite |
Compatibility alias for Bare. | Uses the same profile and capabilities as Bare. |
| Pair | /profile pair |
Work step by step with the user leading. | Standard tools with instructions to agree on the next step before acting. |
| Mentor | /mentor, /profile mentor |
Collaborative second-opinion consulting. Pairs primary model with an advisory strategic model. | Full codebase context, all standard development tools plus the ask_mentor advisory tool. |
| Orchestrator | /orchestrator, /profile orchestrator |
High-level task coordination and multi-agent delegation. | All implementation work is delegated to specialized subagents. |
Switching Modes
Section titled “Switching Modes”- Toggling Plan Mode (
Shift+Tabor/plan): PressingShift+Tabtoggles between Standard mode and Plan mode. In Plan mode, write operations (file editing, file creation, and mutating shell commands) are safely blocked, allowing you to design and explore without risk of unintentional modifications. - Switching Profiles (
/profile <name>): Run/profilefollowed by the profile name (standard,bare,plan,lite,pair,mentor,orchestrator) or run bare/profileto open the interactive selection menu. - Dedicated Slash Commands:
/plan: Toggle Plan mode on or off./lite: Toggle Bare mode on or off (the Lite name is retained for compatibility)./mentor: Toggle Mentor mode on or off./orchestrator: Toggle Orchestrator mode on or off.
Plan Mode Restrictions
Section titled “Plan Mode Restrictions”When Plan mode is active:
- Read-Only Operation: File edits, file creations, and workspace mutations are disabled.
- Safe Command Execution: Only read-only inspection commands (such as directory listings, search, and status checks) are permitted; destructive or mutating shell commands are blocked.
- Structured Planning: The agent focuses on reading code, gathering context, and outlining architecture plans or implementation steps for your review before you switch back to Standard mode to execute them.
Profile Identifiers in Configuration (builtin:)
Section titled “Profile Identifiers in Configuration (builtin:)”When configuring your default profile in settings.json via the app.activeProfileId setting (or when specifying full identifiers in /profile <id>), term2 uses the builtin: prefixed profile identifier:
| Profile Name | Configuration Identifier (app.activeProfileId) |
|---|---|
| Standard | builtin:standard (default) |
| Bare | builtin:bare |
| Plan | builtin:plan |
| Lite | builtin:lite |
| Pair | builtin:pair |
| Mentor | builtin:mentor |
| Orchestrator | builtin:orchestrator |
Everyday CLI flags and slash commands (/profile standard, /plan, --lite) accept the short visible profile names directly.