chore: sync with upstream pingdotgg/t3code main - #44
Merged
Conversation
yordis
commented
Sep 7, 2026
Member
- Upstream's new Antigravity driver resolved its process environment directly, which would have shipped a provider unable to read the fork's 1Password secret references. It now goes through the same resolver as the other five drivers.
- Upstream reworked the legendapp list patch, so hand-resolving it would have silently dropped the fork's scroll-adjust padding fix. The fork's two web sections were rebuilt on top of upstream's patch instead.
- Both sides of the pull request viewer permissions were kept, because upstream's label support and the fork's merge bypass answer different questions and neither supersedes the other.
- Upstream's lockfile was taken wholesale, since the fork adds no dependencies of its own and diverges only by two subpath exports.
- The shared migration chain took upstream's side wholesale so it stays byte-identical, keeping fork schema isolated on its own ledger where id collisions remain impossible.
- Upstream now always appends runtime instructions to the Claude system prompt, so a fork test asserting nothing was appended no longer described the behavior it was written to guard. It now asserts the task-redirect text is absent.
- Ledger entry 0003 was kept. Upstream's subagent rendering predates the merge base on both sides and does not replace the fork's native subagent threads.
- Upstream's new provider-scoped terminal resolves its environment without the fork's secret resolver, so an op:// reference reaches the terminal unresolved. Left alone here to keep this change to the sync itself, as covering that surface extends a divergence and needs its own ledger entry.
…9938) Co-authored-by: Claude Code <noreply@anthropic.com>
…ed (pingdotgg#10435) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…dotgg#10019) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…diff fallback (pingdotgg#9828) Co-authored-by: James <jamescollard2005@gmail.com>
… update depth errors (pingdotgg#7138) Co-authored-by: Julius Marminge <julius0216@outlook.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
…0493) Onboarding listed every directory Claude Code or Codex had ever run in as one flat list of paths, with everything from the last 30 days preselected. On my machine that was 270 rows and 80 preselected. Most of them were Codex scratch folders, worktrees, and one-off questions. I wanted two or three projects and had no fast way to get there. The scanner now reads each candidate's `.git/config` directly, so the client can group clones by origin and show the GitHub `owner/name`. Linked worktrees, Codex scratch directories under `~/Documents/Codex`, `~/Downloads`, and temp roots are no longer offered. Folders that are not git repositories collapse under "Other folders". The default selection requires a git repository with at least three threads. Select all and Select none sit above the list, and each row shows the source icons, thread count, and last activity. On the same machine this drops the list to 162 rows and the default selection to 16. Mobile has no project import step, so there is no mobile change. Created with Claude Fable 5.1 in Claude Code.
Co-authored-by: codex <codex@users.noreply.github.com>
Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
…t upstream's new provider surfaces Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
|
This PR is too large for Bugbot to review. It changes 59,472 lines and 3,857,488 characters. Split the change into smaller pull requests to get a review. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.