Alphabetized reference of Verdent-specific terms and technical concepts.

​
Core Concepts

The main AI assistant that processes requests and executes tools
When conversation history fills context window, limiting the ability to reference earlier content
Indicator in the middle panel showing how much model context is left for the current conversation
Amount of conversation history the AI can reference
System for extending Verdent with external tools
A git repository you’re actively working on. Projects maintain independent session history and configuration.
Specialized AI agent with isolated context for specific tasks (e.g., Verifier)
A specific piece of work within a workspace. Tasks represent individual conversation threads and share the workspace file state.
Function the agent can execute (file_read, bash, glob, etc.)

​
Execution Modes

Full autonomous execution mode where Verdent can read, write, and execute commands without additional approval steps. Default mode for active development.
Read-only planning mode where Verdent analyzes and creates implementation plans without making file modifications. Best for complex changes and unfamiliar codebases.

​
Desktop-Specific Terms

The primary working directory on your chosen branch. Reference point for creating new worktrees, where rebased work ends up.
Isolated working directory linked to the same repository, enabling parallel development without file conflicts
Multiple AI agents working simultaneously in separate worktrees, each with isolated context
Rapid navigation between different projects while maintaining session state
Process of applying changes from a workspace back into the main branch (the branch the workspace was created from)
Pull latest changes from the main branch into the current workspace
In “Rebase to main” and “Sync from main,” the branch name shown is actually the branch of the current Base Workspace, not necessarily master. If your Base Workspace is on a different branch (e.g., develop), the actions will target that branch instead.
Isolated directory for a specific task with a complete copy of repository files and a separate branch

​
Files & Configuration

Project-specific team standards file (project root, version controlled)
MCP server configuration (~/.verdent/mcp.json)
Global personal preferences file (~/.verdent/VERDENT.md)
A git worktree - an isolated working directory linked to the same repository, enabling parallel development

​
Tool-Specific Terms

File search pattern using wildcards (**/*.ts, src/**/*.js)
Specific lines to read from large files (start_line, max_lines)
Regular expression for advanced text searching
file_edit flag to replace multiple identical strings
Maximum time for bash commands: 120 seconds (2 minutes, hard limit)

​
Subagent Terms

Subagent can activate automatically based on request patterns
Subagent’s separate context window (doesn’t consume main context)
Subagent only runs when explicitly @-mentioned
Instructions defining subagent’s behavior and expertise

​
MCP Terms

User-wide MCP configuration (~/.verdent/mcp.json)
External tool/service integrated via Model Context Protocol
Pre-built MCP integration for specific tools or services

​
Performance Terms

Routing tasks to subagents to preserve main context
Multiple subagents running simultaneously
Using line ranges and search to minimize context usage
Main agent managing multiple subagent operations

​
See Also

Core Concepts

Fundamental Verdent concepts

Tool Reference

Complete tool capabilities