feat(config): support config block in TOOLS.md #12

Merged
brad merged 2 commits from fix/bash-env-for-agent-config into main 2026-02-15 14:33:34 -08:00
Owner

Summary

Search for YAML configuration block in AGENTS.md first, then TOOLS.md. Returns the first file containing a valid YAML block.

Why

This enables gradual migration of configuration from AGENTS.md to TOOLS.md without breaking existing setups. Brad can move config blocks thoughtfully while both locations continue to work.

Changes

  • Refactored find_agents_md() into find_workspace() and find_config_file()
  • find_workspace() locates directory containing either AGENTS.md or TOOLS.md
  • find_config_file() checks AGENTS.md first, then TOOLS.md for a YAML block
  • Updated docstrings and debug output

Testing

Tested locally with DEBUG_AGENT_CONFIG=1 - correctly finds YAML block in AGENTS.md and loads config.

## Summary Search for YAML configuration block in AGENTS.md first, then TOOLS.md. Returns the first file containing a valid YAML block. ## Why This enables gradual migration of configuration from AGENTS.md to TOOLS.md without breaking existing setups. Brad can move config blocks thoughtfully while both locations continue to work. ## Changes - Refactored `find_agents_md()` into `find_workspace()` and `find_config_file()` - `find_workspace()` locates directory containing either AGENTS.md or TOOLS.md - `find_config_file()` checks AGENTS.md first, then TOOLS.md for a YAML block - Updated docstrings and debug output ## Testing Tested locally with `DEBUG_AGENT_CONFIG=1` - correctly finds YAML block in AGENTS.md and loads config.
Search for YAML configuration block in AGENTS.md first, then TOOLS.md.
Returns the first file containing a valid YAML block.

This enables gradual migration of configuration from AGENTS.md to
TOOLS.md without breaking existing setups.
brad merged commit 657b35d2b0 into main 2026-02-15 14:33:34 -08:00
brad deleted branch fix/bash-env-for-agent-config 2026-02-15 14:33:35 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
commune/sandbox!12
No description provided.