An agent in Shob is a named configuration that controls how the AI behaves during a session. Each agent specifies which language model to use, what system prompt to apply, which tools are available, how permissions are enforced, and how many reasoning steps it may take. Agents are not different AI services — they are different personas or roles that Shob can adopt, powered by whichever model you have configured.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/shobcoder/shob/llms.txt
Use this file to discover all available pages before exploring further.
Agent Properties
Every agent is defined by the following properties:| Property | Type | Description |
|---|---|---|
name | string | Unique identifier used to select the agent (e.g., build, plan, explore) |
description | string | Explains when the agent should be used; shown in the TUI and used for subagent selection |
mode | primary | subagent | all | Controls where the agent can appear (see below) |
model | provider/model | Override the default model for this agent |
prompt | string | Custom system prompt injected at the start of the conversation |
permission | ruleset | Per-agent permission overrides (merged on top of global defaults) |
steps | number | Maximum agentic iterations before forcing a text-only response |
temperature | number | Sampling temperature for the model |
top_p | number | Top-P nucleus sampling parameter |
variant | string | Provider-specific reasoning effort (e.g., high, max, minimal) |
color | string | Hex color or theme color for the agent chip in the TUI |
hidden | boolean | Hide this subagent from the @ autocomplete menu |
Agent Modes
Themode field determines where an agent can appear in a session:
primary
The agent can be selected directly by the user as the main agent for a session. Primary agents appear in the TUI agent selector and can be specified with
--agent on the CLI.subagent
The agent can only be invoked by another agent using the
task tool. Subagents do not appear in the main agent selector but are available via @name mentions.all
The agent can act as both a primary agent (selected by the user) and a subagent (invoked by other agents). This is the default mode for custom agents created with
shob agent create.Built-in Agents
Shob ships with several native agents out of the box:build — The default primary agent
build — The default primary agent
The
build agent is what runs when you open Shob without specifying another agent. It has read/write/edit/shell access and will ask for your approval on any sensitive operations. It is the only agent with question permission enabled, which means it can ask you clarifying questions mid-task.Mode: primaryplan — Read-only planning agent
plan — Read-only planning agent
The
plan agent operates in a restricted mode: all edit tools are denied except for writing plan files into .shob/plans/. Use it to explore a codebase and produce a structured plan before making any changes.Mode: primaryexplore — Fast codebase exploration subagent
explore — Fast codebase exploration subagent
The
explore agent is optimised for searching and understanding code. It has access to grep, glob, list, read, bash, webfetch, websearch, and codesearch, but cannot write or edit files. Primary agents delegate research tasks to it.When invoking it, specify a thoroughness level in your message: "quick", "medium", or "very thorough".Mode: subagentgeneral — General-purpose multi-step subagent
general — General-purpose multi-step subagent
The
general agent handles complex, multi-step tasks and can be called in parallel with other subagents. It has broad tool access but cannot write to-do lists (todowrite is denied).Mode: subagentcompaction, title, summary — Internal hidden agents
compaction, title, summary — Internal hidden agents
Subagent Delegation
Primary agents can spawn subagents to parallelise or specialise work. A primary agent calls the built-intask tool, providing the name of a subagent and a message. Shob creates a child session for the subagent and runs it independently. The primary agent waits for the child to complete before continuing.
mode: "subagent" or mode: "all" are available for delegation. An agent’s description field is surfaced to the primary agent so it can choose the right subagent for each task.
Listing Agents
Creating Custom Agents
Theshob agent create command generates a new agent interactively or fully non-interactively:
identifier and systemPrompt from your description, then writes a Markdown file with YAML front matter to either .shob/agent/ (project-scoped) or the global config directory.
Available tools you can enable or restrict: bash, read, write, edit, list, glob, grep, webfetch, task, todowrite.
Custom agent file format
Custom agents are Markdown files. The front matter carries the configuration, and the Markdown body becomes the system prompt:.shob/agent/migrations.md
shob.json under the agent key. See Agent Configuration for the full schema.
Setting the Default Agent
If you want a different primary agent to open by default instead ofbuild, set default_agent in your config:
shob.json
mode: "primary" or mode: "all" and must not be hidden.