II.
Page overview
Reference · livepage:docs-user-guide-reference-troubleshooting
Troubleshooting Guide overview
Inspect the raw attributes, linked wiki pages, and inbound or outbound graph edges for page:docs-user-guide-reference-troubleshooting.
Attributes
nodeKind
Page
sourcePath
docs/user-guide/reference/troubleshooting.md
sourceKind
repo-docs
title
Troubleshooting Guide
displayName
Troubleshooting Guide
slug
docs/user-guide/reference/troubleshooting
articlePath
wiki/docs/user-guide/reference/troubleshooting.md
article
[Docs](../index.md) › [Reference](./index.md) › Troubleshooting
# Troubleshooting Guide
**Version:** 1.0
**Last Updated:** 2026-06-22
**Category:** Reference
This guide provides systematic troubleshooting procedures for common Babysitter issues. Each section includes symptoms, diagnosis steps, solutions, and prevention tips.
---
## On this page
- [Installation Issues](#installation-issues)
- [Plugin Issues](#plugin-issues)
- [Adapter Issues](#adapter-issues)
- [Harness Install Issues](#harness-install-issues)
- [Session Binding Issues](#session-binding-issues)
- [Run Execution Issues](#run-execution-issues)
- [Quality Convergence Issues](#quality-convergence-issues)
- [Resumption Issues](#resumption-issues)
- [Performance Issues](#performance-issues)
- [Journal and State Issues](#journal-and-state-issues)
- [Diagnostic Commands Reference](#diagnostic-commands-reference)
- [When to Contact Support](#when-to-contact-support)
---
## Installation Issues
### Node.js Not Found
**Symptoms:**
```
command not found: npm
command not found: node
```
**Diagnosis:**
```bash
which node
which npm
node --version
```
**Solutions:**
1. **Install Node.js via nvm (recommended):**
```bash
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
source ~/.bashrc # or ~/.zshrc
nvm install 22
nvm use 22
```
2. **Direct installation:**
- Download from [nodejs.org](https://nodejs.org/)
- Install the LTS version (22.x)
3. **Verify PATH:**
```bash
echo $PATH | grep -E "(node|npm)"
```
**Prevention:** Use nvm to manage Node.js versions.
---
### Permission Denied During npm Install
**Symptoms:**
```
npm ERR! EACCES: permission denied, mkdir '/usr/local/lib/node_modules'
```
**Diagnosis:**
```bash
npm config get prefix
ls -la $(npm config get prefix)/lib/node_modules/
```
**Solutions:**
1. **Fix npm permissions (recommended):**
```bash
mkdir ~/.npm-global
npm config set prefix '~/.npm-global'
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.zshrc
source ~/.zshrc
```
2. **Reinstall packages:**
```bash
npm install -g @a5c-ai/babysitter@latest
```
**Prevention:** Never use `sudo npm install -g`. Configure npm for user installs.
---
### Core CLI or SDK Module Not Found
**Symptoms:**
```
Error: Cannot find module '@a5c-ai/babysitter-sdk'
```
**Diagnosis:**
```bash
npm list -g @a5c-ai/babysitter-sdk
which babysitter
babysitter --version
echo $PATH
```
**Solutions:**
1. **Repair a stale global shim:**
```bash
npm rm -g @a5c-ai/babysitter @a5c-ai/babysitter-sdk
npm install -g @a5c-ai/babysitter-sdk@latest
babysitter --version
```
2. **Use npm exec with an explicit package/bin when you cannot modify globals:**
```bash
npm exec --yes --package @a5c-ai/babysitter-sdk@latest -- babysitter --version
```
3. **Install the main CLI globally:**
```bash
npm install -g @a5c-ai/babysitter@latest
```
4. **If your code imports the SDK, install it in the project too:**
```bash
npm install @a5c-ai/babysitter-sdk
```
5. **Check PATH includes npm global bin:**
```bash
npm bin -g
# Add this to your PATH if not included
```
**Prevention:** Verify installation with `npm list -g` after installing.
---
### Version Mismatch Errors
**Symptoms:**
```
Error: Incompatible version: sdk@4.x requires babysitter@^4.x
```
**Diagnosis:**
```bash
npm list -g @a5c-ai/babysitter-sdk
```
**Solutions:**
Update all packages to the latest versions:
```bash
npm install -g @a5c-ai/babysitter@latest @a5c-ai/genty-platform@latest
```
**Prevention:** Update all packages together, not individually.
---
### jq Not Found
**Symptoms:**
```
command not found: jq
jq: command not found
```
Many Babysitter diagnostic commands use `jq` for JSON processing. Without it, commands like [journal](./glossary.md) analysis and status inspection will fail.
**Diagnosis:**
```bash
which jq
jq --version
```
**Solutions:**
Install `jq` for your platform:
```bash
# macOS
brew install jq
# Ubuntu/Debian
sudo apt-get install jq
# Fedora/RHEL/CentOS
sudo dnf install jq
# Arch Linux
sudo pacman -S jq
# Windows (Chocolatey)
choco install jq
# Windows (Scoop)
scoop install jq
# Windows (WSL) - use Ubuntu instructions
sudo apt-get install jq
```
**Verify installation:**
```bash
jq --version
# Expected: jq-1.6 or higher
```
**Prevention:** Install `jq` as part of your initial setup. It's a standard tool for working with JSON on the command line.
---
## Plugin Issues
### Plugin Not Appearing in /skills
**Symptoms:**
- `/skills` command doesn't show "babysit"
- "Skill not found: babysit" error
**Diagnosis:**
```bash
claude plugin list
claude plugin list | grep babysitter
```
**Step-by-Step Solution:**
1. **Add marketplace (if not added):**
```bash
claude plugin marketplace add a5c-ai/babysitter-claude
```
2. **Install plugin:**
```bash
claude plugin install --scope user babysitter@a5c.ai
```
3. **Enable plugin:**
```bash
claude plugin enable --scope user babysitter@a5c.ai
```
4. **Restart Claude Code completely:**
- Close all Claude Code windows
- Wait a few seconds
- Reopen Claude Code
5. **Verify:**
```bash
/skills
# Should show "babysit"
```
---
### Plugin Install Fails
**Symptoms:**
```
Error: Plugin 'babysitter@a5c.ai' not found
```
**Diagnosis:**
```bash
claude plugin marketplace list
```
**Solutions:**
1. **Add marketplace first:**
```bash
claude plugin marketplace add a5c-ai/babysitter-claude
```
2. **Check network connectivity:**
```bash
curl -I https://github.com/a5c-ai/babysitter
```
3. **Try updating marketplace:**
```bash
claude plugin marketplace update a5c.ai
```
---
### Plugin Conflicts
**Symptoms:**
- Claude Code behaves unexpectedly
- Other plugins stop working after Babysitter install
**Diagnosis:**
```bash
claude plugin list --all
```
**Solutions:**
1. **Disable and re-enable:**
```bash
claude plugin disable babysitter@a5c.ai
claude plugin enable babysitter@a5c.ai
```
2. **Check for conflicts:**
- Temporarily disable other plugins
- Test Babysitter alone
- Re-enable plugins one by one
---
## Adapter Issues
These cover the host-side `adapters` CLI (package `@a5c-ai/adapters-cli`), which runs and manages harnesses from your shell. See the [Adapters CLI Reference](./adapters-cli.md) for the full command surface. When in doubt, run `adapters doctor` first.
### adapters: command not found
**Symptoms:**
```
adapters: command not found
```
**Diagnosis:**
```bash
which adapters
npm list -g @a5c-ai/adapters-cli
echo $PATH
```
**Solutions:**
1. **Install the CLI globally:**
```bash
npm install -g @a5c-ai/adapters-cli
```
2. **Verify the install and environment:**
```bash
adapters version
adapters doctor
```
3. **Ensure npm global bin is on PATH:**
```bash
npm bin -g
# Add this directory to PATH if missing
```
**Prevention:** Install `@a5c-ai/adapters-cli` as part of initial setup and confirm with `adapters version`.
---
### Node.js Version Too Old for Adapters
**Symptoms:**
```
Error: @a5c-ai/adapters-cli requires Node.js >=20.9.0
```
The `adapters` CLI pins a higher Node floor (>=20.9.0) than the rest of the toolchain (>=20.0.0), so a Node that works for `babysitter` may still be too old for `adapters`.
**Diagnosis:**
```bash
node --version
```
**Solutions:**
1. **Switch to a supported version (22.x LTS recommended):**
```bash
nvm install 22
nvm use 22
```
2. **Re-check:**
```bash
node --version
adapters doctor
```
**Prevention:** Use nvm to keep Node at 22.x LTS.
---
### Harness Not Detected / Adapter Errors
**Symptoms:**
```
Error: adapter not found for agent 'codex'
Error: harness binary for 'gemini' not detected
```
**Diagnosis:**
```bash
adapters doctor
adapters adapters list
adapters adapters detect codex
```
**Solutions:**
1. **Install the missing harness binary:**
```bash
adapters install codex
```
2. **Confirm credentials:**
```bash
adapters auth check
```
3. **If the harness cannot reach a provider natively, let the launcher proxy:**
```bash
adapters launch claude bedrock --with-proxy-if-needed
```
**Prevention:** Run `adapters doctor` after installing or upgrading harnesses.
---
## Harness Install Issues
These cover installing the in-session `/babysitter:*` plugin into a harness with `babysitter harness:install-plugin <harness-key>`. The harness key is **not** always the harness's display name; the authoritative list is the [Install Matrix](../harnesses/install-matrix.md).
### Plugin Not Appearing After Install
**Symptoms:**
- `harness:install-plugin` reports success, but `/babysitter:*` commands are unavailable inside the harness
**Diagnosis:**
```bash
# Re-run targeting the workspace you actually use
babysitter harness:install-plugin <harness-key> --workspace ./my-project
```
**Solutions:**
1. **Restart the harness completely** so it re-discovers installed plugins.
2. **Confirm you installed into the right workspace** with `--workspace`.
3. **Check the harness's continuation model** in the [Hooks](../features/hooks.md) per-harness table. Each harness registers continuation hooks differently — do not assume Claude Code's `Stop`-hook model on another harness.
**Prevention:** Install into the project directory you will run from, and restart the harness after install.
---
### Wrong Harness Key
**Symptoms:**
```
Error: unknown harness key 'gemini'
```
**Diagnosis:**
```bash
# Compare against the documented keys
# e.g. gemini's key is gemini-cli, not gemini
```
**Solutions:**
1. **Use the documented harness key:**
```bash
babysitter harness:install-plugin gemini-cli
```
2. **Look up the correct key** in the [Install Matrix](../harnesses/install-matrix.md) — the key can differ from the harness name.
**Prevention:** Copy the harness key from the Install Matrix rather than guessing from the display name.
---
## Session Binding Issues
In v6, session resolution is **PID-scoped** and harness-agnostic. The session ID is carried in `AGENT_SESSION_ID` (which supersedes the removed/deprecated `BABYSITTER_SESSION_ID` and `CLAUDE_SESSION_ID`). The `--plugin-root` flag has been removed; plugin-root resolution is now handled automatically by the runtime (it injects `BABYSITTER_PLUGIN_ROOT` into hooks for you — it is not a variable you set). See [Configuration](./configuration.md).
### Session Not Bound / In-Session Loop Won't Continue
**Symptoms:**
```
Error: could not resolve agent session for this process
```
- The in-session loop stops advancing, or each turn behaves like a fresh session
**Diagnosis:**
```bash
# Is the harness exporting the session variable?
echo "$AGENT_SESSION_ID"
```
**Solutions:**
1. **Confirm the harness sets `AGENT_SESSION_ID`.** If empty, the harness's continuation hooks may not be installed — see [Hooks](../features/hooks.md) and re-run `babysitter harness:install-plugin <harness-key>`.
2. **If your harness only provides the session via the environment** (not via the PID-scoped store), opt into the legacy env-first behavior:
```bash
export BABYSITTER_TRUST_ENV_SESSION=1
```
3. **Remove stale references** to deprecated variables (`BABYSITTER_SESSION_ID`, `CLAUDE_SESSION_ID`) and the removed `--plugin-root` flag from your scripts and configs.
**Prevention:** Let Babysitter resolve sessions per-PID by default; reserve `BABYSITTER_TRUST_ENV_SESSION=1` for harnesses that genuinely need env-first resolution.
See also: [Error Catalog - Session Binding Errors](./error-catalog.md#session-binding-errors).
---
## Run Execution Issues
### Run Encountered an Error
**Symptoms:**
```
Error: Run encountered an error
at processIteration (process.js:123)
```
**Diagnosis:**
```bash
# Check journal for error details
babysitter run:events <runId> --filter-type RUN_FAILED --json
# View last events
babysitter run:events <runId> --limit 10 --reverse --json
```
**Solutions:**
1. **Identify the cause:**
```bash
jq '.data.error' .a5c/runs/<runId>/journal/$(ls -t .a5c/runs/<runId>/journal/ | head -1)
```
2. **If journal conflict:**
- Ensure no other sessions are running the same workflow
- Delete state cache and rebuild:
```bash
rm .a5c/runs/<runId>/state/state.json
babysitter run:status <runId>
```
3. **If task failure:**
- Fix the underlying issue (missing deps, file not found, etc.)
- Resume:
```bash
/babysitter:call resume --run-id <runId>
```
4. **Ask Claude to analyze:**
```
Analyze the babysitter run error for <runId> and try to recover
```
---
### Task Execution Failed: ENOENT
**Symptoms:**
```
Task failed: test-task-001
Error: ENOENT: no such file or directory
```
**Diagnosis:**
```bash
# Check task details
cat .a5c/runs/<runId>/tasks/<effectId>/task.json | jq .
# Check working directory
pwd
ls -la
```
**Solutions:**
1. **Verify file paths:**
- Check if referenced files exist
- Ensure paths are correct for your system
2. **Install dependencies:**
```bash
npm install
```
3. **Check working directory:**
- Tasks run relative to the run directory
- Verify paths in task definition
---
### Agent Task Timeout
**Symptoms:**
```
Task timeout: agent-task-001
Execution exceeded 120s
```
**Diagnosis:**
```bash
# Check task that timed out
cat .a5c/runs/<runId>/tasks/<effectId>/task.json | jq .
```
**Solutions:**
1. **Reduce task scope:**
- Analyze specific files instead of entire codebase
- Break large tasks into smaller ones
2. **Increase timeout (if necessary):**
```javascript
await ctx.task(analyzeTask, { /* args */ }, {
timeout: 300000 // 5 minutes
});
```
3. **Check API status:**
- Verify Claude API is accessible
- Check for rate limiting
---
### Session Ended Unexpectedly
**Symptoms:**
```
Claude Code session terminated
Run ID: 01KFFTSF8TK8C9GT3YM9QYQ6WG
Status: interrupted
```
**Diagnosis:**
```bash
babysitter run:status <runId> --json
```
**Solutions:**
Resume the run:
```
/babysitter:call resume --run-id 01KFFTSF8TK8C9GT3YM9QYQ6WG
```
Babysitter is designed to be resumable. All progress is preserved.
---
## Quality Convergence Issues
### Quality Score Not Improving
**Symptoms:**
```
Iteration 1: Quality 65/100
Iteration 2: Quality 66/100
Iteration 3: Quality 65/100
...
Iteration 5: Quality 66/100
Target not met: 85/100
```
**Diagnosis:**
```bash
# View effect resolutions
babysitter run:events <runId> --filter-type EFFECT_RESOLVED --json
# Check recommendations
jq '.recommendations' .a5c/runs/<runId>/tasks/*/result.json
```
**Solutions:**
1. **Review feedback:**
- Check what's blocking improvement
- Look for recurring issues
2. **Lower target:**
```
Use babysitter with 75% quality target
```
3. **Increase iterations:**
```
Use babysitter with max 10 iterations
```
4. **Fix blocking issues:**
- Run tests manually: `npm test`
- Check lint: `npm run lint`
- Fix any consistent failures
5. **Review scoring weights:**
- Some criteria may be weighted too heavily
- Adjust in process definition if needed
---
### Iterations Never Converge
**Symptoms:**
- Quality score oscillates without improvement
- Maximum iterations reached without meeting target
**Diagnosis:**
```bash
# Check quality trend
jq -s '[.[] | select(.type == "EFFECT_RESOLVED")] | map({effectId: .data.effectId, status: .data.status})' \
.a5c/runs/<runId>/journal/*.json
```
**Solutions:**
1. **Implement early exit on plateau:**
```javascript
const recentScores = iterationResults.slice(-3).map(r => r.quality);
if (Math.max(...recentScores) - Math.min(...recentScores) < 2) {
ctx.log('Quality plateaued, stopping early');
break;
}
```
2. **Lower target to achievable level**
3. **Review if target is realistic for the codebase**
---
### Inconsistent Quality Scores
**Symptoms:**
- Quality scores vary significantly between iterations
- No clear trend
**Diagnosis:**
```bash
# Check variance in scores
jq -s '[.[] | select(.type == "EFFECT_RESOLVED")] | length' \
.a5c/runs/<runId>/journal/*.json
```
**Solutions:**
1. **Use more deterministic scoring criteria**
2. **Ensure tests are stable (no flaky tests)**
3. **Review agent scoring prompts for consistency**
4. **Use `ctx.now()` instead of `Date.now()` for timestamps**
---
## Resumption Issues
### Cannot Resume Completed Run
**Symptoms:**
- Resume has no effect
- Run state shows "completed"
**Diagnosis:**
```bash
babysitter run:status <runId> --json | jq '.state'
```
**Solutions:**
A completed run cannot be resumed - it's already finished. Create a new run instead.
---
### State Corruption After Manual Edits
**Symptoms:**
- Run behaves unexpectedly
- Events don't match expected behavior
**Diagnosis:**
```bash
# Check journal integrity
jq empty .a5c/runs/<runId>/journal/*.json 2>&1
```
**Solutions:**
1. **Never edit journal files manually**
2. **If state cache corrupted:**
```bash
rm .a5c/runs/<runId>/state/state.json
babysitter run:status <runId> # Rebuilds state
```
3. **If journal corrupted:**
- May need to start a new run
- Backup journal first for analysis
---
### Missing Run Directory
**Symptoms:**
```
Error: Run not found: 01KFFTSF8TK8C9GT3YM9QYQ6WG
```
**Diagnosis:**
```bash
ls -la .a5c/runs/ | grep <runId>
```
**Solutions:**
- Run directory was deleted or never created
- Create a new run instead
- Check if you're in the correct working directory
---
## Performance Issues
### Slow Iteration Execution
**Symptoms:**
- Each iteration takes several minutes
- Tasks run sequentially when they could be parallel
**Diagnosis:**
```bash
# Find slow tasks
jq -s '[.[] | select(.type == "EFFECT_RESOLVED")] | map({effectId: .data.effectId, duration: ((.data.finishedAt | fromdateiso8601) - (.data.startedAt | fromdateiso8601))}) | sort_by(.duration) | reverse | .[0:5]' \
.a5c/runs/<runId>/journal/*.json
```
**Solutions:**
1. **Use parallel execution:**
```javascript
const [coverage, lint, security] = await ctx.parallel.all([
() => ctx.task(coverageTask, {}),
() => ctx.task(lintTask, {}),
() => ctx.task(securityTask, {})
]);
```
2. **Reduce agent task scope**
3. **Set lower iteration limits**
4. **Cache research results between iterations**
---
### High Disk Usage
**Symptoms:**
- `.a5c/` directory growing large
- Disk space warnings
**Diagnosis:**
```bash
du -sh .a5c/
du -h .a5c/runs/* | sort -h | tail -10
```
**Solutions:**
1. **Clean old runs:**
```bash
# List runs by size
du -h .a5c/runs/* | sort -h
# Delete old runs
rm -rf .a5c/runs/<old-run-id>
```
2. **Archive completed runs:**
```bash
tar -czf run-archive.tar.gz .a5c/runs/<runId>
rm -rf .a5c/runs/<runId>
```
3. **Add cleanup to workflow:**
- Periodically clean old runs
- Set up automated cleanup
---
### Memory Issues
**Symptoms:**
```
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
```
**Solutions:**
1. **Increase Node.js memory:**
```bash
export NODE_OPTIONS="--max-old-space-size=4096"
```
2. **Reduce concurrent tasks**
3. **Process smaller batches of files**
---
## Journal and State Issues
### Journal Conflict
**Symptoms:**
```
Error: Journal conflict detected
```
**Diagnosis:**
```bash
# Check if multiple processes running
ps aux | grep babysitter
```
**Solutions:**
1. **Ensure single writer:**
- Only one session should run a workflow at a time
2. **Wait and retry:**
- If previous session crashed, wait a moment
- Resume the run
3. **Rebuild state:**
```bash
rm .a5c/runs/<runId>/state/state.json
babysitter run:status <runId>
```
---
### Events Out of Order
**Symptoms:**
- Events appear in unexpected order
- State doesn't match expectations
**Diagnosis:**
```bash
# Check sequence numbers
jq '.seq' .a5c/runs/<runId>/journal/*.json | sort -n
```
**Solutions:**
- Always use CLI or sort by `seq` field:
```bash
jq -s 'sort_by(.seq)' .a5c/runs/<runId>/journal/*.json
```
- File system listing may not be sorted correctly
---
### State Cache Missing
**Symptoms:**
- CLI commands are slow on first access
- State needs rebuilding
**Diagnosis:**
```bash
ls .a5c/runs/<runId>/state/
```
**Solutions:**
This is normal. The state cache is derived from the journal:
```bash
# Trigger rebuild
babysitter run:status <runId>
```
The cache will be created automatically.
---
## Diagnostic Commands Reference
### Run Status and Events
```bash
# Check run status
babysitter run:status <runId> --json
# View all events
babysitter run:events <runId> --json
# View last N events
babysitter run:events <runId> --limit 10 --reverse --json
# Filter by event type
babysitter run:events <runId> --filter-type EFFECT_RESOLVED --json
# Find failures
babysitter run:events <runId> --filter-type RUN_FAILED --json
```
### Task Information
```bash
# List pending tasks
babysitter task:list <runId> --pending --json
# View task details
cat .a5c/runs/<runId>/tasks/<effectId>/task.json | jq .
# View task result
cat .a5c/runs/<runId>/tasks/<effectId>/result.json | jq .
```
### System Checks
```bash
# Check core CLI version
babysitter --version
# Check the host-side Adapters CLI and run a health check
adapters version
adapters doctor
# Check installed packages
npm list -g @a5c-ai/babysitter @a5c-ai/adapters-cli @a5c-ai/genty-platform
# Check plugin status (Claude Code)
claude plugin list | grep babysitter
```
### Journal Analysis
```bash
# Count events by type
jq -s 'group_by(.type) | map({type: .[0].type, count: length})' \
.a5c/runs/<runId>/journal/*.json
# Find failed tasks
jq 'select(.type == "EFFECT_RESOLVED" and .data.status == "error")' \
.a5c/runs/<runId>/journal/*.json
# Check effect resolutions
jq 'select(.type == "EFFECT_RESOLVED") | {effectId: .data.effectId, status: .data.status}' \
.a5c/runs/<runId>/journal/*.json
```
---
## When to Contact Support
Contact support if you experience:
1. **Persistent crashes** that cannot be resolved with troubleshooting
2. **Data corruption** that affects the journal or state
3. **Security concerns** about the tool behavior
4. **Bugs** that are reproducible with clear steps
### How to Report Issues
1. **Gather information:**
- OS and version
- Node.js version: `node --version`
- Claude Code version: `claude --version`
- Babysitter CLI version: `babysitter --version`
- Full error message and stack trace
- Steps to reproduce
2. **Include diagnostic output:**
```bash
babysitter run:status <runId> --json > diagnostic.json
babysitter run:events <runId> --limit 50 --reverse --json >> diagnostic.json
```
3. **Create issue at:**
[GitHub Issues](https://github.com/a5c-ai/babysitter/issues)
4. **For discussions:**
[GitHub Discussions](https://github.com/a5c-ai/babysitter/discussions)
---
## Related Documentation
- [FAQ](./faq.md) - Common questions answered
- [Error Catalog](./error-catalog.md) - Error messages explained
- [Configuration Reference](./configuration.md) - Environment variables (including `AGENT_SESSION_ID` and `BABYSITTER_TRUST_ENV_SESSION`)
- [Adapters CLI Reference](./adapters-cli.md) - The host-side `adapters` CLI
- [Install Matrix](../harnesses/install-matrix.md) - Supported harnesses and their harness keys
- [Installation Guide](../getting-started/installation.md) - Setup instructions
- [Run Resumption](../features/run-resumption.md) - Recovery procedures
---
## Next steps
- **Next:** [Error Catalog](./error-catalog.md)
- **Related:** [FAQ](./faq.md), [Configuration](./configuration.md)
---
**Document Status:** Complete
**Last Updated:** 2026-06-22
documents
[]
Outgoing edges
None.
Incoming edges
contains_page1
- page:docs-user-guide-reference·PageUser Guide Reference