Non-technical install path + OAuth/CORS guidance for Excel add-in
Session from pi-for-excel-sessions on Hugging Face by thomasmustier · MIT · condensed by Coders Talk
Enable a non-technical user to install the Pi for Excel add-in and use OAuth logins, addressing GitHub issue #16 by improving the install docs, prod manifest flow, and CORS/proxy guidance.
- +0Prompt · +0Work on issue #16: let a non-technical user install the add-in easily, including using their own logins even if that requires CORS guidance. Work in a separate worktree.
- +0mAgent did · +0mSet up an isolated git worktree/branch, read the issue, existing install docs, manifest files, proxy validation code and welcome/login UI to understand current CORS/proxy setup before making changes.
- +4mAgent did · +4mUpdated proxy-validation.ts, welcome-login.ts, provider-login.ts, init.ts, cors-proxy-server.mjs, README.md and rewrote docs/install.md to standardize on port 3003, clarify OAuth/CORS remediation steps, and provide a full non-technical install walkthrough.
- +7mAgent did · +7mRan npm run check, npm install, build, and test:security to validate the changes; all passed.
- +11mPrompt · +11mYes please do and open a PR.
- +12mAgent did · +12mCommitted the changes, pushed the branch, and opened PR #114 'feat(install): improve non-technical install and OAuth proxy guidance' against main.
- +14mPrompt · +14mSleep 5 minutes for automated review to run, then another 5 if nothing shows up.
- +14mAgent did · +14mPolled PR #114 after 5 minutes: all CI checks (build, CodeQL, dependency review, Vercel preview) passed with no human review comments; issue #16 closed after merge.
- +24mPrompt · +24mReview all work since the last release and cut a new GitHub release with notes, tagged as experimental.
- +24mAgent did · +24mDiffed all merged PRs since v0.3.0-pre, created prerelease v0.4.0-pre targeting main with the manifest.prod.xml asset attached and auto-generated notes, then edited the notes to add a curated experimental summary on top.
- +28mOutcome · +28mIssue #16 closed via merged PR #114; experimental release v0.4.0-pre published with manifest.prod.xml asset and curated release notes; team moved on to next open issues (#80, #19, #18, #13).
Next time I'd ask for the worktree isolation and the full install/CORS rewrite in one go, since that's basically what happened and it went smoothly with the agent doing its own research before editing. The main correction that mattered was catching that it hadn't actually checked in on the automated PR review loop correctly the first time, and later reminding it that issue #111 was already closed before it tried to re-scope work — that kept us from duplicating effort.