fuse: Instructions file for Codex

Agent Instructions

This project uses epos for task and ticket tracking.

Quick Reference

epos ready              # Find available work
epos blocked            # Find blocked work
epos show <id>          # View ticket details
epos claim <id> -o "$AGENT_ID"    # Claim work
epos close <id> -r "Reason"       # Complete work
epos new "Title"        # Create a new ticket

Non-Interactive Shell Commands

ALWAYS use non-interactive flags with file operations to avoid hanging on confirmation prompts.

Shell commands like cp, mv, and rm may be aliased to include -i (interactive) mode on some systems, causing the agent to hang indefinitely waiting for y/n input.

Use these forms instead:

# Force overwrite without prompting
cp -f source dest           # NOT: cp source dest
mv -f source dest           # NOT: mv source dest
rm -f file                  # NOT: rm file

# For recursive operations
rm -rf directory            # NOT: rm -r directory
cp -rf source dest          # NOT: cp -r source dest

Other commands that may prompt:

• scp - use -o BatchMode=yes for non-interactive
• ssh - use -o BatchMode=yes to fail instead of prompting
• apt-get - use -y flag
• brew - use HOMEBREW_NO_AUTO_UPDATE=1 env var

Issue Tracking with epos

IMPORTANT: This project uses epos for ALL task and ticket tracking. Do NOT use markdown TODOs, task lists, direct .tickets/ edits, or other tracking methods.

Why epos?

• Dependency-aware: Track blockers and relationships between tickets
• Plain markdown: Tickets are readable directly from .tickets/
• Agent-optimized: Ready work detection, claims/leases, validation, JSON export, and partial ID matching
• Prevents duplicate tracking systems and confusion

Quick Start

Check for ready work:

epos ready
epos blocked

Create new tickets:

epos new "Ticket title" --type bug --priority 2 --body "Detailed context"
epos new "Follow-up task" --body "What this issue is about"