Expose built-in assistant docs in Files workspace (Excel add-in)
Session from pi-for-excel-sessions on Hugging Face by thomasmustier · MIT · condensed by Coders Talk
Let the AI assistant access its own docs (README, extension guides) via the filesystem so users can just ask about them, without gating everything behind the experimental files flag.
- +0Prompt · +0Enable the agent to have context on its own docs (README, extension docs) via the filesystem, available regardless of /experimental setting, at least for assistant docs.
- +0mAgent did · +0mExplored the tool registry, experimental gates, files workspace, and docs layout, then proposed adding a separate always-on read-only `assistant_docs` tool distinct from the experimental `files` workspace.
- +5mIntervention · +5mDeveloper rejected the separate-tool idea and asked why files was experimental at all, insisting docs should live in the same Files UI users already see, with no extra tool or flow.Why: I didn't want a second tool/flow for something conceptually the same as the files workspace users already interact with — one UI, one mental model.
- Break · 37m away, not counted
- +6mPrompt · +6mPlease implement, open a PR, sleep and poll for CI/review feedback, resolve conflicts, and merge once green — but be careful not to clobber parallel local work in the main worktree.
- +6mAgent did · +6mBuilt a bundled `assistant-docs/` namespace merged into the existing files workspace (read-only, always available), updated the files tool/UI/tests, gated write/delete only behind the experiment flag, opened PR #136, fixed a reviewer-flagged path-collision bug, rebased on main, and merged.
- Break · 4h 50m away, not counted
- +58mPrompt · +58mGreat. What's next?
- +58mAgent did · +58mRefactored the 800+ line files-dialog into filtering/status helper modules, added quick-filter chips (All/Built-in docs/Current workbook) and tests, then opened PR #140.
- +1h 11mOutcome · +1h 11mPR #136 and PR #140 both merged into main, shipping built-in assistant docs plus quick filters in the shared Files workspace UI.
Next time I'd open with the constraint I ended up stating later: reuse the existing Files UI/tool, no separate assistant-only flow — that would've saved a full exploration-and-pitch round trip. The correction that mattered was pushing back on the agent's instinct to bolt on a new `assistant_docs` tool; once I redirected it to fold docs into the existing workspace, the implementation, tests, and PR flow went smoothly with only a real reviewer bug (path collisions) to fix, plus a lot of noisy but harmless Vercel rate-limit failures during CI polling.