Repository navigation
Show FlyBot branding in the web UI (header, About, settings, update popups) - #108
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7a65ef5204
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| .bt-return:active{transform:scale(.96)} | ||
| .bt-return .bt-mark{display:inline-flex;flex:none;line-height:0} | ||
| .bt-return .bt-mark svg{width:100%;height:100%;overflow:visible} | ||
| .bt-return .bt-mark,.bt-return .bt-flybot-mark{display:inline-flex;flex:none;line-height:0} |
There was a problem hiding this comment.
In Classic Agent mode, especially with a collapsed sidebar or dark theme, index.js withdraws SHELL_CSS and leaves only RETURN_CSS for BotReturn. FlyBotMark has no inline fill attributes, while every .bt-flybot-wing, .bt-flybot-body, and .bt-flybot-eye fill rule lives in the withdrawn shell stylesheet, so all SVG parts fall back to black, the face disappears, and the only return icon can be nearly invisible. Mirror the logo fill rules in RETURN_CSS or make the mark self-colored.
Useful? React with 👍 / 👎.
| export function brandTitle(title) { | ||
| const text = String(title ?? '') | ||
| if (text === 'DeepSeek Harness' || text === 'DS Bot') return 'FlyBot' | ||
| if (text.endsWith(' — DeepSeek Harness')) return `${text.slice(0, -' — DeepSeek Harness'.length)} — FlyBot` |
There was a problem hiding this comment.
When the shell supplies a title whose prefix also contains DS Bot, such as DS Bot — DeepSeek Harness, this early return changes only the suffix and initially leaves the old brand; if the observed title changes later, the observer's follow-up pass can then turn it into FlyBot — FlyBot. Apply both replacements in one idempotent transformation so existing DS Bot-named sessions/workspaces become a single FlyBot-branded title.
Useful? React with 👍 / 👎.
| h('button', { type: 'button', className: 'bt-soft bt-soft-sm', onClick: copyReport }, t('Copy'))), | ||
| preview ? h('div', { className: 'bt-set-row bt-fb-preview' }, h('pre', { tabIndex: 0, 'aria-label': t('Diagnostics') }, report?.markdown || t('Loading…'))) : null, | ||
| h(Row, { label: t('GitHub issue'), hint: t('Opens a new issue in the DS Bot repository with all of this filled in. Nothing is sent until you submit it there.') }, | ||
| h(Row, { label: t('GitHub issue'), hint: t('Opens a new issue in the FlyBot repository with all of this filled in. Nothing is sent until you submit it there.') }, |
There was a problem hiding this comment.
In the Report on GitHub flow, openIssue consumes next.issuesUrl, but core/src/host/diagnostics.js still returns the hard-coded Fei2411/DeepSeek-Bot tracker, so this new hint promises the FlyBot repository while opening upstream DS Bot. The same mismatch appears in About, where the new “Star FlyBot” copy uses the unchanged upstream repository metadata; retain upstream wording or retarget these actions so reports and stars are not misdirected.
Useful? React with 👍 / 👎.
7a65ef5 to
fb20fc7
Compare
The sidebar still showed the upstream whale mark and "DS Bot". Replace
user-visible chrome with FlyBot (header mark from docs/images/logo.svg,
About, settings, update popups as "FlyBot core {version}", diagnostics,
zh copy). Package names, the update-check, and repository URLs stay
upstream.
Co-authored-by: Danyang Chen <birfychen@gmail.com>
Head branch was pushed to by a user without write access
fb20fc7 to
bc91824
Compare
The web UI chrome still said DS Bot. This changes user-visible branding to FlyBot (en + zh) via the patch layer (0014-flybot-branding), uses docs/images/logo.svg for the header mark, and labels updates as FlyBot core {version}. ds-bot/ is untouched; package names, the update check and upstream links are unchanged. Local verify passed (arch-docs, bundle check, patches check, core/social/tree tests).