Matt Bruce
8f4f979c85
New specialized agents: - ios-dev: iOS/Swift/SwiftUI development - web-dev: Next.js/React/web development - research: Research and analysis tasks Each agent has: - Own agent.json config with specialized system prompt - Auto-loaded relevant skills - Domain-specific best practices and rules - Proper model configuration Also added: - SPECIALIZED_AGENTS.md documentation - CLI_README_TEMPLATE.md for reference
1.6 KiB
1.6 KiB
Memory Log — February 22, 2026
CLI Tools for Gantt Board File Attachments - COMPLETE
Problem: Browser relay requires manual clicks, making it impossible for me to attach files when Matt is remote.
Solution: Created CLI tools using Supabase service role key (bypasses auth, no browser needed).
New Scripts Created:
attach-file.sh- Attach any file to a task via APIview-attachment.sh- View attachment content via APIgantt-task-crud.sh- Already existed, task CRUD operations
How attachments work:
- Files converted to base64 data URLs
- Stored inline in task's
attachmentsarray (JSON) - No separate storage bucket needed
- Accessible via web UI immediately
Tested on:
- Task: https://gantt-board.vercel.app/tasks/33ebc71e-7d40-456c-8f98-bb3578d2bb2b (iOS MRR Research)
- File: ios-mrr-research-2026-02-21.md (16,491 bytes)
- Result: ✅ Attached, status set to done, local file deleted
Key Lesson Learned:
Matt accesses gantt board remotely. I MUST be able to attach files without browser clicks. CLI/API is the only acceptable solution. Browser relay requiring manual extension connection is UNACCEPTABLE for remote access use case.
Single Source of Truth:
- Files attached to gantt board tasks ONLY
- Local copies deleted immediately after attachment confirmed
- No duplicates in workspace
Critical Requirements Going Forward:
- Every app must have programmatic API access (no browser click dependencies)
- File attachments must work via CLI for remote access
- Verify via API, not trust subagent "done" reports
- Document all CLI tools in MEMORY.md immediately