E4 Code is a personal fork of pingdotgg/t3code. Each patch on top of upstream is listed here by commit subject.
Lets E4 Code install next to T3 Code without sharing state.
- App ID
com.eliasschneider.e4code, product name "E4 Code" (no "Beta" suffix; nightlies stay "E4 Code (Nightly)"). - Data in
~/.e4and Electron profilee4codeinstead of~/.t3andt3code-v2. - Linux executable, desktop entry and
.debpackage renamed toe4code; packaged WM class matches the E4 desktop identity; upstream’s unused runtime--classswitch stays removed. Updatable AppImages use versionlessE4-Code/E4-Code-Nightlynames, retaining upstream’s old-path restoration after an update. - Desktop updates, CLI archives, the install scripts (including remote setup commands and the CLI self-install fallback), release links and the GitHub star prompt point at
stonith404/e4code. - Windows installer running-app prompts recognize E4 Code and E4 Code (Nightly), retaining upstream's legacy-name detection.
- Managed policy uses E4-specific files, macOS preference domain, Windows registry key and generated policy templates, so T3 Code can be managed separately. Startup profiles go to
.e4/startup-profiles. - Web bootstrap and runtime titles use E4 branding and channel labels, retaining upstream’s thread/project window titles.
- Tests updated to the new names.
README.mdopens with a short fork section listing the user-facing patches, andAGENTS.mdends with the fork's rules for agents.
Keeps upstream's three icon designs (black production, night-sky nightly, blueprint dev) and swaps the T3 wordmark for a geometric E4.
text.svgin the dev, nightly and prod Icon Composer projects carries the E4 mark; the devannotations.svgdimension lines follow the new glyphs.- iOS, universal, Windows, web favicon and Android assets regenerated with
icons:exportandicons:export:android. The macOS pre-Tahoe PNGs are composed from the universal export (824 body inset 100, soft shadow) because the export only works in the Icon Composer GUI. - Android monochrome and notification marks redrawn by hand at the same bounds as upstream's T3 silhouettes.
- Installable web icons (192 and 512 pixels) use the E4 mark for every channel; these are resized from the universal E4 exports.
T3Wordmarkin web and mobile, the mobile widget mark,assets/prod/logo.svg, the DMG backgrounds and the mobile showcase favicon use the E4 path. Component and file names stay as upstream's to keep syncs small.
e4-release.yml replaces upstream's release.yml, which only runs in pingdotgg/t3code. It reuses release-desktop.yml on GitHub-hosted runners without T3 Connect, npm, AUR, web, mobile or Discord publishing. Nightlies run hourly when main has changed (at least 6 hours apart). Stable releases come from a vX.Y.Z tag or a manual dispatch. A manual dispatch can set skip_checks to skip the release quality checks and tests. Upstream's other workflows are disabled in the repository settings.
macOS builds are ARM64 only, on macOS 15 runners to avoid the macOS 26 ARM64 capacity queue.
Upstream syncs rebase these patches onto upstream's main, so check-nightly-release.cjs also releases a main that diverged from the last nightly, instead of skipping it.
Lets the in-app updater install new builds on Macs that trust the fork's certificate. Squirrel.Mac only swaps in an update whose signature matches the running app, which ad hoc builds never do.
.github/actions/import-mac-signing-identityimportsCSC_LINKinto a keychain, trusts it as a root when it is self-signed (otherwise macOS lists no valid identity) and returns the identity name. The CLI archive and desktop jobs both use it.- When
CSC_LINKis set but the Apple notarization secrets are not, the desktop job passes the identity asT3CODE_DESKTOP_MAC_SIGN_IDENTITY.build-desktop-artifact.tsthen setsmac.identitywith hardened runtime and notarization off, instead of upstream's--signedpath that needs a provisioning profile. - The CLI's imported identity is passed to both archive signing and the deferred notarization gate, preserving upstream's parallel notarization and publication safety check.
- Gatekeeper still shows the unverified-developer dialog on first launch, since only notarized Developer ID builds skip it.
- Each Mac that should receive in-app updates trusts the certificate once:
security add-trusted-cert -r trustRoot -p codeSign -k ~/Library/Keychains/login.keychain-db e4code-signing.cert.pem. The first switch from an ad hoc build to a signed one is a manual DMG install.
A Review surface in the right panel (+ menu, R, or the thread details Review item) for a thread's local changes, laid out like GitKraken: changed files in a sidebar, one whole file at a time beside it. The diff panel is upstream's. Opening Review maximizes the panel when it was last left maximized on the Review tab (t3code.reviewMaximized), and a maximized Review collapses the thread sidebar until it is restored. The surface opens with the file sidebar focused, where ↑/↓ step through files, R toggles Reviewed and M toggles Check later.
- Scopes Changes, Uncommitted and Unpushed: commits ahead of the upstream, or of the base branch when there is none (
review.getDiffPreviewwithunpushed: true). The base branch is always the automatic one. The chosen scope is remembered per thread, and until one is chosen it follows the diff panel (Uncommitted, otherwise Changes). Unpushed includes upstream's change-type metadata, keeping added, deleted and renamed sidebar icons accurate before patches load. - The sidebar shows the files as a list (change-type icon, start-truncated path) or a tree; in both, reviewed files are dimmed, flagged files highlighted, and only the selected file shows its mark icon (the tree through
:has()on its decoration icons inpierre-tree-theme.ts). It resizes like the file explorer (t3code.reviewSidebarWidth). The selected file renders with Pierre'sexpandUnchanged, loading full contents throughloadDiffFilesinto a copy of the shared parsed diff, and scrolls to its first change once loaded. A strip beside it marks where the file changed (reviewOverview.ts), and clicking it scrolls there. Line comments go to the composer as in the diff panel, with the same environment and project context for dictation. Large diffs load per file throughuseReviewFilePatches. - In the working-tree scopes the shown file is always editable unless it is deleted or its patch was truncated. Pierre edits only complete diffs and cannot complete a new file's patch, so
reviewDiff.tsrebuilds it from the patch's one hunk.AnnotatableCodeViewpasses aneditflag andonItemEditChangethrough to Pierre's CodeView, and edits save through the file editor's save sessions, which refresh the diff once confirmed. While a save is pending the shown diff stays pinned, because Pierre replaces the edited document with any new diff. - Per-file Reviewed and Check later marks, stored client-side per thread and scope (
t3code:review-marks:v1). A reviewed file whose diff blobs change reads as Changed. Shown in the file header, the sidebar and the panel header. - The sidebar's Review guide view: a Markdown summary (with a mermaid diagram when it helps) and the changed files grouped in reading order, which the previous/next buttons then follow. It reuses the PR review guide writer (including project-specific provider fallback settings) and its coverage normalization on a snapshot of the local changes (a checkpoint commit in a temporary worktree), with its own prompt. Generation failures keep a short model-settings hint and expandable diagnostics, so retry stays reachable. Guides are kept under
review-guides/in the state directory, keyed by workspace, scope and base ref (review.getGuide,review.generateGuide). - The thread details Changes row follows the diff panel's selected scope: Uncommitted uses the working-tree totals and a turn its checkpoint totals, both already on the client. Any other selection, such as a commit or a tool call, falls back to upstream's branch Changes totals:
resolveChangesTotalswith upstream's branch-range diff preview, so the remembered base ref and hidden whitespace count as in the diff panel, and upstream's dirty-working-tree totals when branch totals are empty. Deleting a thread clears its saved review scope along with upstream's panel state. - Web and desktop only; mobile only widens a type.
Settings → MCP servers adds, edits, toggles and removes MCP servers per environment, and picks which Claude and Codex instances get each one.
mcpServersin server settings (packages/contracts/src/mcpServer.ts): stdio or Streamable HTTP. Env, header, client secret and session values go to the secret store. Patches need the providers-manage scope, since a stdio server is a host command.- The Claude and Codex adapters add the servers beside
t3-codewhen a session starts, including when Codex reloads an idle thread for an MCP app request. Botht3-codeand Codex's direct-onlyt3-code-directregistration are reserved names. Claude's T3 instructions now key on thet3-codeentry, not on any MCP server being present. - OAuth:
McpServersdiscovers metadata (RFC 9728/8414), runs PKCE through/oauth/mcp-servers/callback, keeps the session inoauthSessionand refreshes it. Without a client ID it signs in as the client ID metadata document athttps://e4.elias.li/mcp-client.jsonwhen the server accepts one and the redirect is loopback, and otherwise registers a client per sign-in (RFC 7591). Providers reach OAuth servers through/mcp-servers/<name>with their T3 session credential, and the proxy adds the access token. projectEnabledoverridesenabledper project.McpServersreads the thread's project only when some server has an override, both for session config and the OAuth proxy. In a project scope the settings switch writes the override, and a server added there starts off environment-wide.- With several environments in the settings scope,
McpServersmerges their lists by name and writes each change to every environment.draftForEnvironmentdrops saved secrets an environment does not hold, and sign-in stays per environment. - Web only; the mobile app has no MCP server screen.
Settings → General → Clawdmeter shows the environment's threads on a Clawdmeter ESP32 display paired with its computer over Bluetooth, with no companion app.
clawdmeterEnabledin server settings (default off).ClawdmeterServicefollows it, so the server only loads@stoprocent/nobleand touches Bluetooth while it is on.ClawdmeterLinkscans for the board's service, connects, writes JSON to its RX characteristic with response, and follows its TX (dismiss) and REQ (send everything again) notifications. It reconnects every 10 s while the board is away, and skips the disconnect call for a board that already left, since noble never settles it on macOS.ClawdmeterDisplayturns the thread list into the firmware's sessions-only payload: up to sixsstiles, with states fromprojectThreadAwarenessV2(needs you, working, done for a minute, then idle until settled),e/esturn events,m/xalerts for pending requests and failed runs, and anrpheartbeat every minute.- Bluetooth bindings load on demand through
createRequire, so standalone CLI builds can resolve the packaged native dependency. - The desktop app declares
NSBluetoothAlwaysUsageDescription, since the server runs inside it. - Web and desktop only; the mobile app has no setting for it.
The server no longer sends product usage events to upstream's PostHog ingest unless T3CODE_TELEMETRY_ENABLED=true. AnalyticsService defaults the flag to false, and the onboarding and About copy say so. Relay and mobile tracing already stay off in E4 builds, which carry no relay tracing config.
Upstream's #33131 dropped plan mode from the composer along with its Labs toggle. This patch restores the plan-mode parts of that commit and always offers them, so there is no setting.
- Web: the Build/Plan chip in the composer and its overflow menu,
/planand/default, Shift+Tab, the plan follow-up banner, and Implement, Refine and Implement in a new thread (useProposedPlanSend). Queued, resumed and multi-model sends carry the thread's interaction mode again. - Mobile:
/planand/defaulton threads and New task, and sends use the draft's interaction mode.resolveProviderInteractionModeinthread-outbox-modelis exported for this. - Providers with
showInteractionModeToggle: falsestill run in build mode and show no toggle. - The OpenCode plan agent stays hidden from the traits picker unless selected, as upstream has it.
- User docs: a Plan mode section in
composer.mdand the per-provider notes.