The Fellowship's Agents

Palantir

Background Monitor

Watches quest progress via task metadata during fellowship execution. Detects stuck quests (no phase change in extended periods), scope drift (implementation diverging from plan), and file conflicts between parallel quests. Reports issues to Gandalf for intervention.

Enabled by default. Spawns at 2+ active quests. Configure via palantir.enabled and palantir.minQuests in settings.

Quest Runner

Quest Executor

The workhorse agent that executes the quest lifecycle. Uses the fellowship CLI binary for gate management, status checks, and phase transitions. Each quest runner operates in its own isolated git worktree, ensuring parallel quests never interfere with each other.

Spawned by Gandalf during fellowships. Uses /quest skill internally.

Balrog

Adversarial Validator

Attacks the implementation before it reaches review. Analyzes the quest diff for failure modes, writes targeted test cases using the project's existing test framework, runs them, and delivers a severity-ranked findings report. Critical and High findings block the Review gate until addressed.

Spawned by quest between Implement and Review. No gates, no commits — findings only.

Scout

Research Agent

Autonomous research agent for questions that need investigation but not code changes. Explores the codebase, reads documentation, and optionally spawns a fresh adversarial validator subagent to verify findings. Produces structured reports with confidence levels.

Spawned via scout: <question> in fellowship descriptions. No gates, no hooks, no commits.

How They Work Together

You
task descriptions, gate approvals
Palantir
alerts (stuck, drift, conflicts)
Gandalf Coordinator
Quest Runners
spawn with task gate submissions, status updates
Balrog
spawn pre-review findings report
Scouts
spawn with question research findings