docs: Add agent-relay CLI patterns for direct visibility and log tailing#124
Merged
khaliqgant merged 12 commits intomainfrom Jan 9, 2026
Merged
docs: Add agent-relay CLI patterns for direct visibility and log tailing#124khaliqgant merged 12 commits intomainfrom
khaliqgant merged 12 commits intomainfrom
Conversation
…yspojrciaw)" This reverts commit 812fd18.
…lay.json
BREAKING CHANGE: Trajectory config moved from repo-level (.relay/config.json)
to user-level centralized location.
Changes:
- Move relay config to ~/.config/agent-relay/relay.json (not repo-specific)
- Config applies globally to all projects via AGENT_RELAY_CONFIG_DIR env var
- Users opt-in to repo storage via central config: {"trajectories": {"storeInRepo": true}}
- Remove repo-level .relay/config.json (no longer needed)
- Update trajectory/config.ts with new getAgentRelayConfigDir() pattern
- Document trajectory system in lead.md with configuration instructions
Rationale:
- Centralized config avoids repo-specific clutter
- Single config applies to all projects in user's workspace
- Follows existing agent-relay pattern (AGENT_RELAY_CONFIG_DIR)
- Survives repo deletion; user can manage globally
Architecture:
- Primary: $AGENT_RELAY_CONFIG_DIR/relay.json
- Default: ~/.config/agent-relay/relay.json
- Trajectories stored in ~/.config/agent-relay/trajectories/<project-hash>/
- Optional: storeInRepo: true puts .trajectories/ in repo
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
…il spawn Clarify that TRAJECTORIES_PROJECT and TRAJECTORIES_DATA_DIR are explicitly set after spreading process.env, ensuring config-based values take precedence over any parent shell environment variables.
Member
Author
Follow-up Work Captured in BeadsDuring this refactoring, we discovered an architectural limitation with the Trail CLI that has been documented as a beads task for future work: bd-trail-config: Trail CLI Config File ReadingIssue: Trail CLI currently only reads trajectory storage location from the Solution: Trail CLI should be enhanced to read Benefits:
Implementation Notes:
See: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Enhanced lead agent documentation with practical agent-relay CLI patterns for real-time visibility and debugging.
Changes
agent-relay agents:logswith follow mode for real-time monitoringWhy This Matters
-fflag enables live monitoring while agents workFiles Changed
Testing
agent-relay agentsagent-relay agents:logs <name> -fagent-relay agents:logs -h