0 Fork 0

Files

T

History

yetone 7bdb0b34e8 ui-preview: the sandbox gets made-up data before it is recorded, so a change that only shows with data can be seen (owner: pr-preview 的时候有时候没有数据压根儿测不了，能否帮忙造一些假数据之后再测啊)

seed.mjs write fills the fresh home before magpie starts:
- a Sub2API relay (three keys, rotate, 5h/1d/7d windows, a month of balance history), Acme Cloud and a routing group with a rule;
- 30 days of requests from Claude Code, Codex, OpenCode and Gemini CLI over models priced on models.dev, at different speeds, with TTFT, cache reads, reasoning, sessions, accounts and a few 429/502s;
- 308 Claude Code and 94 Codex session files, more than a page, many never sent through magpie;
- two ChatGPT accounts signed in to Codex (Pro with credits, Plus near its limit) with five weeks of quota history;
- library skills from GitHub (one author with two repositories) and a folder, and some only in the agents' folders.

seed.mjs serve stays up as the mock: the fake providers in the Chat, Responses and Anthropic APIs, the relay's /v1/usage, and, as magpie's HTTPS_PROXY, chatgpt.com's usage and Codex models under a certificate from a CA that run.sh makes. Every other host is tunnelled as it is, so DeepSeek still answers for real. The warm-up also goes through the relay, Acme and the group, and record.mjs's guide says what the sandbox now has.

Checked by running run.sh in a Linux container:
- the Codex cards are read live, not stale, and their history draws;
- the relay's windows and balance trend show;
- every model is priced;
- sessions list 200 of 402;
- the warm-ups all pass.
Then record.mjs ran for real (DeepSeek planning, Playwright) on 6e53ee1f's diff (#1031). It planned and shot the skills page's author groups, with GitHub skills above and local below.

2026-10-06 22:49:36 +08:00

.gitignore

ci: a pull request that changes the UI shows it — the real app built from the PR, run with a real DeepSeek key, screenshots and, when the change spans pages or needs clicking, an mp4 recording with the pointer, its trail and every click drawn in, in a fixed block at the foot of the PR's description (the user: 如果某个PR涉及了UI/UX改动，那么就把这个PR中的Magpie真实的运行起来…录屏中一定要画出鼠标指针的位置，以及鼠标的轨迹，以及鼠标的点击; 一定要贴在原始的PR Description的下面的固定区域).

2026-09-30 14:22:13 +08:00

cursor.js

2026-09-30 14:22:13 +08:00

package.json

2026-09-30 14:22:13 +08:00

publish.mjs

ci: a UI preview goes by the diff, not the PR's description — on #287 the description (out of date) promised a 用量小数位 setting the code doesn't have, and the preview repeated it as the change, captioned a screenshot "默认 0 位" of a setting that wasn't there. The planner is told the description may be wrong, to plan and summarise from the diff, and what the sandbox lacks (subscription quotas above all); the preview now says, apart from the summary (改动（按代码）), where the description and the code disagree (描述与代码不符) and what the sandbox can't show (沙盒里看不到). Tested locally with run.sh on #287 's code: it names the missing setting, says the sandbox has only a DeepSeek balance and no percentage windows, and shows the two places the change would be.

2026-09-30 15:45:23 +08:00

README.md

ui-preview: the sandbox gets made-up data before it is recorded, so a change that only shows with data can be seen (owner: pr-preview 的时候有时候没有数据压根儿测不了，能否帮忙造一些假数据之后再测啊)

2026-10-06 22:49:36 +08:00

record.mjs

2026-10-06 22:49:36 +08:00

run.sh

2026-10-06 22:49:36 +08:00

seed.mjs

2026-10-06 22:49:36 +08:00

README.md

UI preview

.github/workflows/ui-preview.yml shows reviewers what a pull request does to the UI. When a PR touches internal/gui/assets/ or the GUI's Go code, or carries the ui-preview label, the workflow does this:

publish.mjs detect decides whether the PR is a UI change. It puts a "recording…" note in a fixed block at the foot of the PR description, between  and .
run.sh builds the PR's magpie (nogui) and runs magpie web in a fresh home, with DeepSeek added as a real provider. Before magpie starts, seed.mjs fills that home with made-up data, so a change that only shows with data can be seen:
- two more providers, one a Sub2API relay with three keys, 5h/1d/7d windows and a month of balance history, and a routing group;
- 30 days of requests from four agents over several models at different speeds, with sessions, cache reads and a few errors;
- more than 200 Claude Code and Codex session files;
- two ChatGPT accounts signed in to Codex, with quota windows and five weeks of quota history;
- skills in the library from GitHub (one author with two repositories) and a local folder, and a few only in the agents' own folders.
seed.mjs then stays up as a mock: it answers the fake providers, the relay's usage, and chatgpt.com's account usage. For chatgpt.com it is magpie's HTTPS proxy, with a certificate from a CA that run.sh makes; every other host goes through it untouched. run.sh sends a few real requests through the gateway, then runs:
record.mjs, which:
- gives DeepSeek the diff and outlines of the real pages;
- has it plan scenes: what to click, hover, type and capture;
- walks the plan in Chromium at 2x, with cursor.js drawing the pointer, its trail and each click. It always takes screenshots. When the change spans pages or needs interaction, it also records an mp4, never a GIF. If the key shows up on screen at any point, everything is thrown away.
publish.mjs publish puts the files under pr-<n>/<sha>/ on the ui-previews branch, which GitHub Pages serves, and rewrites the block in the description:
- the video's poster links to the player page, since GitHub won't embed a video it didn't host;
- the screenshots are shown inline.

Security: the recording job runs the PR's code without asking anyone. Any PR's code can therefore read DEEPSEEK_API_KEY (environment ui-preview), so the key there should have a low spending limit. That job has no write access, and the job that writes never runs the PR's code.

To run it locally (run.sh builds and starts magpie itself):

cd .github/ui-preview && npm install && npx playwright install chromium
DEEPSEEK_API_KEY=… DIFF_FILE=pr.diff PR_TITLE=… ./run.sh ../.. /tmp/out

To re-run it for a PR, use gh workflow run ui-preview.yml -f pr=<n>.