@orderful/droid 0.33.1 → 0.34.1

package/dist/tools/brain/skills/brain/references/workflows.md

@@ -9,7 +9,7 @@ Detailed procedures for each brain operation.
 **Steps:**
 
 1. **Read config first (MANDATORY)**
-   - Run `droid config brain` and parse the JSON output
+   - Run `droid config --get tools.brain` and parse the JSON output
    - Use the `brain_dir` value from the config
    - If `brain_dir` is not configured, **ask the user** where they want brain docs stored
    - **Do NOT skip this step or assume defaults**
@@ -48,7 +48,7 @@ Detailed procedures for each brain operation.
 **Steps:**
 
 1. **Read config first (MANDATORY)**
-   - Run `droid config brain` and parse the JSON output
+   - Run `droid config --get tools.brain` and parse the JSON output
    - Use the `brain_dir` and `inbox_folder` values from the config
    - If `brain_dir` is not configured, **ask the user** where they want brain docs stored
    - **Do NOT skip this step or assume defaults**
@@ -78,8 +78,8 @@ Detailed procedures for each brain operation.
    - Related work or prior decisions?
 
 7. **Add placeholder comments** for sections needing user input:
-   - Get `user_mention` from config: `droid config brain | grep user_mention`
-   - Use `> @{user_mention}` for placeholders (e.g., `> @fry - Please provide requirements`)
+   - Get `user_mention` from config: `droid config --get user_mention`
+   - Use `> @{user_mention}` for placeholders (e.g., `> @{user} - Please provide requirements`)
    - **CRITICAL:** NEVER use `@droid` - that's for user-to-AI comments, not AI-to-user
 
 8. **Write the doc** with template structure and initial context
@@ -95,7 +95,7 @@ Detailed procedures for each brain operation.
 **Steps:**
 
 1. **Read config first (MANDATORY)**
-   - Run `droid config brain` and parse the JSON output
+   - Run `droid config --get tools.brain` and parse the JSON output
    - Use the `brain_dir` and `inbox_folder` values from the config
    - If `brain_dir` is not configured, **ask the user** where they want brain docs stored
    - **Do NOT skip this step or assume defaults**
@@ -165,7 +165,7 @@ Detailed procedures for each brain operation.
 2. **Read active doc**
 
 3. **Check preserve_comments setting:**
-   - Run `droid config comments` and parse the JSON output
+   - Run `droid config --get tools.comments` and parse the JSON output
    - Use the `preserve_comments` value (default: `true`)
 
 4. **Find all `> @droid` comments**
@@ -174,9 +174,9 @@ Detailed procedures for each brain operation.
 5. **For each comment:**
    - Show the comment and surrounding context
    - Address the question/request
-   - Add response as blockquote with user's mention (from `droid config brain`): `> @{user_mention} Your response here`
-   - Example: `> @fry Yes, the index covers that query pattern.`
-   - **CRITICAL:** NEVER use `@droid` in your responses. Use `@{user_mention}` from config (e.g., `@fry`)
+   - Add response as blockquote with user's mention (from `droid config --get tools.brain`): `> @{user_mention} Your response here`
+   - Example: `> @{user} Yes, the index covers that query pattern.`
+   - **CRITICAL:** NEVER use `@droid` in your responses. Use `@{user_mention}` from config (e.g., `@{user}`)
    - **CRITICAL:** Always include the `>` prefix to maintain blockquote formatting
    - **CRITICAL:** If `preserve_comments: true`, keep the original `@droid` comment and add your response below it. Do NOT remove the original comment.
 
@@ -216,7 +216,7 @@ Detailed procedures for each brain operation.
 **Steps:**
 
 1. **Read config first (MANDATORY)**
-   - Run `droid config brain` and parse the JSON output
+   - Run `droid config --get tools.brain` and parse the JSON output
    - Use the `brain_dir` value from the config
    - If `brain_dir` is not configured, **ask the user** where they want brain docs stored
    - **Do NOT skip this step or assume defaults**

package/dist/tools/coach/skills/coach/SKILL.md

@@ -53,11 +53,11 @@ plan → AI scaffolds → human implements → AI coaches → iterate → ship
 | -------------------- | -------- | ------------------------------------------------------- |
 | `scaffold_verbosity` | `medium` | How detailed hints are: `minimal`, `medium`, `detailed` |
 
-<!-- Note: @mention is the target, not author. @fry = AI talking TO user, @droid = user talking TO AI -->
-> @fry Not yet - droid currently shows config as free text input. But we could add an `enum` type to the config schema that presents as a select dropdown in the TUI. Good feature request - want me to create an issue for it?
+<!-- Note: @mention is the target, not author. @{user} = AI talking TO user, @droid = user talking TO AI -->
+> @{user} Not yet - droid currently shows config as free text input. But we could add an `enum` type to the config schema that presents as a select dropdown in the TUI. Good feature request - want me to create an issue for it?
 > @droid yes lets do that
 
-Run `droid config coach` to get the merged configuration.
+Run `droid config --get tools.coach` to get the merged configuration.
 
 ---
 
@@ -136,9 +136,9 @@ Run `droid config coach` to get the merged configuration.
 **Example inline comments:**
 
 ```typescript
-// @fry Why did you choose a Map here instead of an object?
-// @fry What happens if this promise rejects?
-// @fry I notice you're mutating state directly - was that intentional?
+// @{user} Why did you choose a Map here instead of an object?
+// @{user} What happens if this promise rejects?
+// @{user} I notice you're mutating state directly - was that intentional?
 ```
 
 > @droid is it worth mentioning using the correct comment syntax for the file language? We typically use TS but could be others

package/dist/tools/codex/skills/codex/SKILL.md

@@ -59,7 +59,7 @@ The codex skill includes three git scripts. **Always use these instead of raw gi
 ### Read Operations (search, load, list)
 
 ```bash
-droid config codex | droid exec codex git-preamble --config -
+droid config --get tools.codex | droid exec codex git-preamble --config -
 # Then proceed with the read
 ```
 
@@ -67,12 +67,12 @@ droid config codex | droid exec codex git-preamble --config -
 
 ```bash
 # 1. Start write (runs preamble + creates branch)
-droid config codex | droid exec codex git-start-write --config - --branch codex/{action}-{name}
+droid config --get tools.codex | droid exec codex git-start-write --config - --branch codex/{action}-{name}
 
 # 2. Make your changes (write files)
 
 # 3. Finish write (commit + PR + return to main)
-droid config codex | droid exec codex git-finish-write --config - \
+droid config --get tools.codex | droid exec codex git-finish-write --config - \
   --message "{commit message}" \
   --pr-title "{PR title}" \
   --pr-body "{PR description}"
@@ -141,7 +141,7 @@ fi
 
 ## Configuration
 
-**ALWAYS run `droid config codex` first and parse the JSON output.**
+**ALWAYS run `droid config --get tools.codex` first and parse the JSON output.**
 
 | Setting          | Default                           | Description                   |
 | ---------------- | --------------------------------- | ----------------------------- |
@@ -200,7 +200,7 @@ Parse args by splitting on ` -- `. First part = search terms, second part = inst
 
 1. **Run preamble first:**
    ```bash
-   droid config codex | droid exec codex git-preamble --config -
+   droid config --get tools.codex | droid exec codex git-preamble --config -
    ```
 2. **Read `{codex_repo}/index.yaml`** - this contains all entry names and aliases for fast lookup
 3. Match `{name}` against index keys and aliases (case-insensitive, partial match)

package/dist/tools/codex/skills/codex/references/creating.md

@@ -31,7 +31,7 @@ A project named '{name}' already exists. Did you mean to load it?
 ### 3. Start Write Operation
 
 ```bash
-droid config codex | droid exec droid-codex git-start-write --config - --branch codex/new-{name}
+droid config --get tools.codex | droid exec droid-codex git-start-write --config - --branch codex/new-{name}
 ```
 
 This runs the git preamble (ensures clean main + pulls latest) and creates the branch.
@@ -62,7 +62,7 @@ If user provides context, fill in what we know:
 ### 7. Finish Write Operation
 
 ```bash
-droid config codex | droid exec droid-codex git-finish-write --config - \
+droid config --get tools.codex | droid exec droid-codex git-finish-write --config - \
   --message "feat(codex): scaffold {name} project" \
   --pr-title "New project: {name}" \
   --pr-body "Scaffold for {name} project"

package/dist/tools/codex/skills/codex/references/decisions.md

@@ -42,7 +42,7 @@ I'll add this decision. Can you clarify:
 ### 3. Start Write Operation
 
 ```bash
-droid config codex | droid exec droid-codex git-start-write --config - --branch codex/decision-{short-summary}
+droid config --get tools.codex | droid exec droid-codex git-start-write --config - --branch codex/decision-{short-summary}
 ```
 
 ### 4. Read and Update DECISIONS.md
@@ -77,7 +77,7 @@ Update the `updated` field in frontmatter to today's date.
 ### 5. Finish Write Operation
 
 ```bash
-droid config codex | droid exec droid-codex git-finish-write --config - \
+droid config --get tools.codex | droid exec droid-codex git-finish-write --config - \
   --message "decision({active}): {summary}" \
   --pr-title "Decision: {summary}" \
   --pr-body "{full decision text}"

package/dist/tools/codex/skills/codex/references/loading.md

@@ -6,7 +6,7 @@ Detailed procedure for loading entries from the codex.
 
 **IMPORTANT:** Use the index file for fast lookups. This avoids expensive file-by-file searching.
 
-1. **Get codex repo path** by running `droid config codex` and parsing the JSON output
+1. **Get codex repo path** by running `droid config --get tools.codex` and parsing the JSON output
 2. **Read the index file** at `{codex_repo}/index.yaml`:
    ```yaml
    # index.yaml structure

package/dist/tools/codex/skills/codex/references/topics.md

@@ -46,7 +46,7 @@ Ask user or infer:
 ### 4. Start Write Operation
 
 ```bash
-droid config codex | droid exec droid-codex git-start-write --config - --branch codex/topic-{name}
+droid config --get tools.codex | droid exec droid-codex git-start-write --config - --branch codex/topic-{name}
 ```
 
 ### 5. Read Template
@@ -124,7 +124,7 @@ codebase_paths:
 ### 7. Finish Write Operation
 
 ```bash
-droid config codex | droid exec droid-codex git-finish-write --config - \
+droid config --get tools.codex | droid exec droid-codex git-finish-write --config - \
   --message "topic: add {name}" \
   --pr-title "Topic: {name}" \
   --pr-body "New topic from codebase exploration"

package/dist/tools/codex/skills/codex/scripts/git-finish-write.d.ts

@@ -6,7 +6,7 @@
  * and returning to main.
  *
  * Usage:
- *   droid config codex | droid exec droid-codex git-finish-write --config - \
+ *   droid config --get tools.codex | droid exec droid-codex git-finish-write --config - \
  *     --message "feat: add new topic" \
  *     --pr-title "New topic: caching" \
  *     --pr-body "Added exploration of caching patterns"

package/dist/tools/codex/skills/codex/scripts/git-finish-write.ts

@@ -6,7 +6,7 @@
  * and returning to main.
  *
  * Usage:
- *   droid config codex | droid exec droid-codex git-finish-write --config - \
+ *   droid config --get tools.codex | droid exec droid-codex git-finish-write --config - \
  *     --message "feat: add new topic" \
  *     --pr-title "New topic: caching" \
  *     --pr-body "Added exploration of caching patterns"
@@ -194,7 +194,7 @@ const { config, message, prTitle, prBody } = parseArgs(args);
 if (!config) {
   console.log(JSON.stringify({
     success: false,
-    error: 'Missing --config. Usage: droid config codex | droid exec droid-codex git-finish-write --config - --message "..." --pr-title "..."',
+    error: 'Missing --config. Usage: droid config --get tools.codex | droid exec droid-codex git-finish-write --config - --message "..." --pr-title "..."',
   }));
   process.exit(1);
 }

package/dist/tools/codex/skills/codex/scripts/git-preamble.d.ts

@@ -6,7 +6,7 @@
  * Run this before ANY codex operation (read or write).
  *
  * Usage:
- *   droid config codex | droid exec droid-codex git-preamble --config -
+ *   droid config --get tools.codex | droid exec droid-codex git-preamble --config -
  *
  * What it does:
  *   1. Checkout main (abort any stuck merge/rebase)

package/dist/tools/codex/skills/codex/scripts/git-preamble.ts

@@ -6,7 +6,7 @@
  * Run this before ANY codex operation (read or write).
  *
  * Usage:
- *   droid config codex | droid exec droid-codex git-preamble --config -
+ *   droid config --get tools.codex | droid exec droid-codex git-preamble --config -
  *
  * What it does:
  *   1. Checkout main (abort any stuck merge/rebase)
@@ -135,7 +135,7 @@ const { config } = parseArgs(args);
 if (!config) {
   console.log(JSON.stringify({
     success: false,
-    error: 'Missing --config. Usage: droid config codex | droid exec droid-codex git-preamble --config -',
+    error: 'Missing --config. Usage: droid config --get tools.codex | droid exec droid-codex git-preamble --config -',
   }));
   process.exit(1);
 }
@@ -143,7 +143,7 @@ if (!config) {
 if (!config.codex_repo) {
   console.log(JSON.stringify({
     success: false,
-    error: 'Missing codex_repo in config. Run: droid config codex --set codex_repo=~/path/to/codex',
+    error: 'Missing codex_repo in config. Run: droid config --get tools.codex --set codex_repo=~/path/to/codex',
   }));
   process.exit(1);
 }

package/dist/tools/codex/skills/codex/scripts/git-start-write.d.ts

@@ -6,7 +6,7 @@
  * and creating a new branch.
  *
  * Usage:
- *   droid config codex | droid exec droid-codex git-start-write --config - --branch codex/new-feature
+ *   droid config --get tools.codex | droid exec droid-codex git-start-write --config - --branch codex/new-feature
  *
  * Options:
  *   --config <json>   Config with codex_repo path (required)

package/dist/tools/codex/skills/codex/scripts/git-start-write.ts

@@ -6,7 +6,7 @@
  * and creating a new branch.
  *
  * Usage:
- *   droid config codex | droid exec droid-codex git-start-write --config - --branch codex/new-feature
+ *   droid config --get tools.codex | droid exec droid-codex git-start-write --config - --branch codex/new-feature
  *
  * Options:
  *   --config <json>   Config with codex_repo path (required)
@@ -143,7 +143,7 @@ const { config, branch } = parseArgs(args);
 if (!config) {
   console.log(JSON.stringify({
     success: false,
-    error: 'Missing --config. Usage: droid config codex | droid exec droid-codex git-start-write --config - --branch <name>',
+    error: 'Missing --config. Usage: droid config --get tools.codex | droid exec droid-codex git-start-write --config - --branch <name>',
   }));
   process.exit(1);
 }

package/dist/tools/comments/skills/comments/SKILL.md

@@ -19,10 +19,10 @@ Leave comments for the AI using `> @droid`:
 > @droid Can you add error handling here?
 ```
 
-The AI will respond with `> @{user_mention}` (configured in droid setup, e.g., `@fry`):
+The AI will respond with `> @{user_mention}` (configured in droid setup, e.g., `@{user}`):
 
 ```markdown
-> @fry I think this approach is solid. One consideration...
+> @{user} I think this approach is solid. One consideration...
 ```
 
 ## Tag Convention
@@ -39,19 +39,19 @@ The directionality can be confusing. The @mention is the **target**, not the aut
 Think of it like addressing someone in conversation:
 
 - "Hey @droid, what do you think?" → User talking TO the AI
-- "Good point @fry, here's my take..." → AI talking TO the user
+- "Good point @{user}, here's my take..." → AI talking TO the user
 
 **Examples:**
 
 ```markdown
 > @droid Can you explain this function? ← User asking AI
-> @fry This function calculates the hash... ← AI responding to user
+> @{user} This function calculates the hash... ← AI responding to user
 
 > @droid Should we refactor this? ← User asking AI
-> @fry Yes, I'd suggest extracting... ← AI responding to user
+> @{user} Yes, I'd suggest extracting... ← AI responding to user
 ```
 
-**Never flip this.** When responding to a `@droid` comment, always use `@{user}` (e.g., `@fry`) because you're addressing the user, not yourself.
+**Never flip this.** When responding to a `@droid` comment, always use `@{user}` (e.g., `@{user}`) because you're addressing the user, not yourself.
 
 ## When NOT to Use
 
@@ -84,7 +84,7 @@ When you find a `@droid` marker:
 
 #### Pass 1: Read & Analyse
 
-1. **Read config first:** Run `droid config comments` and check `preserve_comments` setting (default: `true`)
+1. **Read config first:** Run `droid config --get tools.comments` and check `preserve_comments` setting (default: `true`)
 2. Search for ALL `> @droid` comments (and any configured `ai_mentions`) in the specified scope
 3. If there's a `git diff`, check those files first for relevant context
 4. **Read all comments before responding** - understand the full picture
@@ -109,11 +109,11 @@ When you find a `@droid` marker:
 
 ## Configuration
 
-Configured via `droid config comments` (merges global config with skill overrides):
+Configured via `droid config --get tools.comments` (merges global config with skill overrides):
 
 ```yaml
 # Override the user mention (default: from global config)
-user_mention: "@fry"
+user_mention: "@{user}"
 
 # Additional AI mentions to recognize (e.g., if you're used to @claude)
 ai_mentions: "@claude"

package/dist/tools/plan/skills/plan/SKILL.md

@@ -24,8 +24,8 @@ Task-scoped planning for PRs, tickets, and small features. Lighter than `/tech-d
 ## Configuration
 
 Uses config from dependencies:
-- `droid config brain` → `brain_dir`, `inbox_dir`
-- `droid config comments` → `user_mention`
+- `droid config --get tools.brain` → `brain_dir`, `inbox_dir`
+- `droid config --get tools.comments` → `user_mention`
 
 ## Commands
 

package/dist/tools/plan/skills/plan/references/workflows.md

@@ -7,8 +7,8 @@ Detailed command flows for the plan skill.
 ### Step 1: Read Configuration
 
 ```bash
-droid config brain   # → brain_dir, inbox_dir
-droid config comments # → user_mention
+droid config --get tools.brain   # → brain_dir, inbox_dir
+droid config --get tools.comments # → user_mention
 ```
 
 If brain not configured, ask user for `brain_dir` location.

package/dist/tools/project/skills/project/SKILL.md

@@ -26,7 +26,7 @@ Chat history disappears. Projects persist.
 
 ## Configuration
 
-**IMPORTANT:** Run `droid config project` first to get the merged configuration.
+**IMPORTANT:** Run `droid config --get tools.project` first to get the merged configuration.
 
 | Setting        | Default      | Description                                        |
 | -------------- | ------------ | -------------------------------------------------- |

package/dist/tools/project/skills/project/references/creating.md

@@ -5,7 +5,7 @@
 ## Procedure
 
 1. **Read config first**
-   - Run `droid config project` and parse the JSON output
+   - Run `droid config --get tools.project` and parse the JSON output
    - Use `projects_dir` (required - if not configured, inform user to set it up)
    - Use `preset` if configured (markdown or obsidian)
 
@@ -77,7 +77,7 @@ Bridge shared organizational knowledge (codex) to personal working memory (proje
    - If `{name} --from codex:{codex-name}` → use custom project name
 
 2. **Load codex entry**
-   - Run `droid config codex` and get `codex_repo` from the JSON output
+   - Run `droid config --get tools.codex` and get `codex_repo` from the JSON output
    - Sync: `git -C {codex_repo} pull --rebase --quiet`
    - Locate `{codex_repo}/projects/{name}/`
    - If not found → error with suggestions from available projects

package/dist/tools/project/skills/project/references/loading.md

@@ -7,7 +7,7 @@
 ## Procedure
 
 1. **Determine projects directory**
-   - Run `droid config project` and parse the JSON output
+   - Run `droid config --get tools.project` and parse the JSON output
    - Use the `projects_dir` value
    - If not configured → inform user to create `~/.droid/skills/project/overrides.yaml` with `projects_dir: /path/to/projects`
 

package/dist/tools/tech-design/skills/tech-design/SKILL.md

@@ -28,8 +28,8 @@ The `/tech-design` skill brings tech design authoring into the same AI-augmented
 
 Before using tech-design, verify:
 
-1. **Brain skill configured:** Run `droid config brain` and check if `brain_dir` is set
-2. **Codex skill configured:** Run `droid config codex` and check if `codex_repo` is set
+1. **Brain skill configured:** Run `droid config --get tools.brain` and check if `brain_dir` is set
+2. **Codex skill configured:** Run `droid config --get tools.codex` and check if `codex_repo` is set
 3. **gh CLI:** Required for PR workflows
 
 If prerequisites fail, guide user to configure:

package/dist/tools/tech-design/skills/tech-design/references/publish.md

@@ -25,7 +25,7 @@ if [ ! -f "$research_doc_path" ]; then
 fi
 
 # Codex repo must be configured (read from codex skill config)
-codex_repo=$(droid config codex | grep -o '"codex_repo": *"[^"]*"' | cut -d'"' -f4)
+codex_repo=$(droid config --get tools.codex | grep -o '"codex_repo": *"[^"]*"' | cut -d'"' -f4)
 if [ -z "$codex_repo" ]; then
   echo "Error: Codex not configured."
   echo "Set up with: /codex"
@@ -134,7 +134,7 @@ Use codex git scripts for safety:
 
 ```bash
 # Use codex skill's git-start-write script
-droid config codex | droid exec droid-codex git-start-write \
+droid config --get tools.codex | droid exec droid-codex git-start-write \
   --config - \
   --branch "codex/tech-design-$project"
 ```
@@ -232,7 +232,7 @@ After approval:
 - [ ] Begin implementation"
 
 # Use codex skill's git-finish-write script
-droid config codex | droid exec droid-codex git-finish-write \
+droid config --get tools.codex | droid exec droid-codex git-finish-write \
   --config - \
   --message "$commit_msg" \
   --pr-title "$pr_title" \

package/dist/tools/tech-design/skills/tech-design/references/start.md

@@ -12,8 +12,8 @@
 
 Check that required tools are configured:
 
-- **Brain skill:** Run `droid config brain` and check if `brain_dir` is set
-- **Codex skill:** Run `droid config codex` and check if `codex_repo` is set
+- **Brain skill:** Run `droid config --get tools.brain` and check if `brain_dir` is set
+- **Codex skill:** Run `droid config --get tools.codex` and check if `codex_repo` is set
 
 If prerequisites fail, guide user to configure:
 
@@ -92,7 +92,33 @@ Research for tech design: {brief description from PRD}
 
 Explore code repositories to discover patterns, similar features, integration points, and dependencies.
 
-**Note:** The specific repositories to search should be discovered from the project context or user's workspace. Common patterns to look for:
+**Note:** The specific repositories to search should be discovered from the project context or user's workspace.
+
+#### Unknown Repo Handling
+
+When exploring and user mentions a repo not in the repos registry:
+
+1. Check available repos: `droid config --get repos`
+2. If repo not found in the list, prompt the user:
+   - "I don't have '{repo-name}' in your repos registry. Would you like to add it?"
+3. If user confirms, ask for the repository path:
+   - Suggest common patterns: `~/src/github.com/{repo-name}` or `~/code/{repo-name}`
+4. Add the repo: `droid repos add {repo-name} --path {path} --description "{optional description}"`
+5. Proceed with exploration using the newly registered repo
+
+**Example:**
+
+```
+User: "Check the orderful-workspace repo for similar patterns"
+Assistant: I don't have 'orderful-workspace' in your repos registry. Would you like to add it?
+User: Yes
+Assistant: What's the path to orderful-workspace? (e.g., ~/src/github.com/orderful-workspace)
+User: ~/src/github.com/orderful-workspace
+Assistant: [Runs: droid repos add orderful-workspace --path ~/src/github.com/orderful-workspace --description "Main monorepo"]
+Added orderful-workspace to your repos. Now exploring for similar patterns...
+```
+
+**Common patterns to look for:**
 
 - **Existing similar features:**
   - Search for related functionality

package/dist/tools/tech-design/skills/tech-design/references/think.md

@@ -227,7 +227,7 @@ Which would you prefer?
 **If option 3 (create comment):**
 
 ```bash
-# Get user_mention from: droid config tech-design
+# Get user_mention from: droid config --get user_mention
 # Add comment to thought doc:
 
 > @{user} Explored events vs polling for status updates

package/dist/tools/wrapup/skills/wrapup/references/subagent-prompts.md

@@ -31,7 +31,7 @@ Output format:
 ```
 Read {session_brief_path} for session context.
 
-First, run `droid config project` to get the project skill configuration.
+First, run `droid config --get tools.project` to get the project skill configuration.
 Parse the JSON output to find the `projects_dir` value.
 
 If `projects_dir` is not set, skip project file analysis.
@@ -56,7 +56,7 @@ If no active project found, note that and skip.
 ```
 Read {session_brief_path} for session context.
 
-First, run `droid config brain` and parse the JSON output for the `brain_dir` setting.
+First, run `droid config --get tools.brain` and parse the JSON output for the `brain_dir` setting.
 If not configured, skip brain doc analysis.
 
 If configured:
@@ -78,7 +78,7 @@ Output:
 ```
 Read {session_brief_path} for session context.
 
-Run `droid config codex` and check if `codex_repo` is set.
+Run `droid config --get tools.codex` and check if `codex_repo` is set.
 If not configured, skip codex analysis.
 
 If the session involved:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@orderful/droid",
-  "version": "0.33.1",
+  "version": "0.34.1",
   "description": "AI workflow toolkit for sharing skills, commands, and agents across the team",
   "type": "module",
   "bin": {

package/src/bin/droid.ts

@@ -9,6 +9,12 @@ import { uninstallCommand } from '../commands/uninstall';
 import { updateCommand } from '../commands/update';
 import { tuiCommand } from '../commands/tui';
 import { execCommand } from '../commands/exec';
+import {
+  reposListCommand,
+  reposAddCommand,
+  reposRemoveCommand,
+  reposGetCommand,
+} from '../commands/repos';
 import { getVersion } from '../lib/version';
 
 const version = getVersion();
@@ -32,6 +38,39 @@ program
   .option('-s, --set <key=value>', 'Set a config value')
   .action(configCommand);
 
+// Repos command with subcommands
+const repos = program
+  .command('repos')
+  .description('Manage repository registry');
+
+repos
+  .command('list')
+  .description('List all registered repos')
+  .option('--json', 'Output as JSON')
+  .action((options) => reposListCommand(options));
+
+repos
+  .command('add [name]')
+  .description('Add a repo to the registry')
+  .option('-p, --path <path>', 'Repository path')
+  .option('-d, --description <desc>', 'Repository description')
+  .action((name, options) =>
+    reposAddCommand(name, options.path, options.description),
+  );
+
+repos
+  .command('remove [name]')
+  .description('Remove a repo from the registry')
+  .action((name) => reposRemoveCommand(name));
+
+repos
+  .command('get <name>')
+  .description('Get a specific repo (JSON output for scripts)')
+  .action((name) => reposGetCommand(name));
+
+// Default: list repos if no subcommand
+repos.action(() => reposListCommand());
+
 program
   .command('tools')
   .description('Browse and manage available tools')

package/src/commands/config.ts

@@ -42,8 +42,14 @@ export function getToolConfig(toolName: string): ToolConfig {
 }
 
 export async function configCommand(tool?: string, options?: ConfigOptions): Promise<void> {
-  // If tool provided, return merged config as JSON
+  // DEPRECATED: If tool provided, return merged config as JSON
+  // TODO: Remove in v1.0 - use `droid config --get tools.<tool>` instead
   if (tool) {
+    console.log(
+      chalk.yellow(
+        `Warning: 'droid config <tool>' is deprecated. Use 'droid config --get tools.${tool}' instead.`,
+      ),
+    );
     const toolConfig = getToolConfig(tool);
     console.log(JSON.stringify(toolConfig, null, 2));
     return;
@@ -94,6 +100,13 @@ export async function configCommand(tool?: string, options?: ConfigOptions): Pro
 
     const [, key, rawValue] = match;
 
+    // Guard repos key - should use `droid repos add/remove` instead
+    if (key === 'repos' || key.startsWith('repos.')) {
+      console.error(chalk.red('Cannot set repos via --set.'));
+      console.log(chalk.gray('Use: droid repos add/remove'));
+      process.exit(1);
+    }
+
     // Try to parse as JSON, otherwise use as string
     let value: unknown;
     try {