Skip to content

fix(desktop): keep NeoCode entries separate from T3 Code - #211

Open
PsychedelicShayna wants to merge 2 commits into
nightlyfrom
fix/neocode-desktop-coexistence-20261111
Open

PsychedelicShayna wants to merge 2 commits into
nightlyfrom
fix/neocode-desktop-coexistence-20261111

Conversation

@PsychedelicShayna

@PsychedelicShayna PsychedelicShayna commented Nov 11, 2026 •

Copy link
Copy Markdown
Owner

What

Use NeoCode-owned Linux desktop-entry names for both packaged and development portal/URL registration. Preserve an existing upstream T3 Code entry in the xdg-utils regression fixture. Permit the new NeoCode capture identities in the GNOME capture service while keeping upstream clients supported.
Linux packages now use neocode for both the executable and Debian package identity, rather than sharing upstream's t3code executable/desktop filename and package ownership.

Document the separate-backend-home requirement; this change deliberately does not migrate saved data or change URL schemes.

Why

Owner: "I never said replace T3Code, I said add NeoCode to the menu."

NeoCode currently writes com.t3tools.T3Code.desktop, the upstream-owned filename. The installed hidden handler points at NeoCode, and three local scratch installers also explicitly updated that upstream filename. Those local installers were corrected separately to update only the NeoCode launcher; scratch scripts are not repository files.

Default backend state still collides at ~/.t3/userdata. Official upstream v0.1.8 uses a separate Chromium profile, but safe simultaneous launch also requires its own T3CODE_HOME and isolated XDG config/data paths while the older NeoCode install remains running. No live userdata was modified, no running NeoCode was stopped, and no upstream binary was launched against the shared home.

Testing

Not run locally: delegated assignment reserves code verification for the main agent. Added upstream-file-preservation assertion to the existing isolated xdg-utils test; updated desktop identity expectations. Existing GNOME whitelist tests enumerate every allowed client and therefore cover the new identities when run.

Attempted polite admission for installation: rejected by memory admission (53.0 GiB outside polite jobs versus 50 GiB budget, no tier fits; 60-second timeout). No upstream installation or smoke launch was performed. Source-reviewed official v0.1.8 DesktopConfig, DesktopStatePaths, DesktopUserData and desktop handler implementation for isolation options.

Signed commit verified with git verify-commit HEAD.


  • vp check and vpr typecheck pass (CI runs both; locally run only the checks for the touched scope, per AGENTS.md › Verifying)
  • Tested locally
  • Before/after images (video for motion) uploaded to GitHub for UI changes, not committed (if user-facing)

No rendered UI change; menu/runtime identity only. No screenshots captured. Leave this PR unmerged as explicitly requested.

Model: openai-codex/gpt-6.1-sol. Harness: NeoPi.

Use NeoCode-owned Linux desktop entry names so portal and URL registration no longer rewrite upstream's entry. Retain storage and URL schemes, and allow the new capture identities in the shared GNOME service. Cover preservation of an existing upstream desktop file and document safe profile separation.

Checks not run: worker assignment leaves verification to main; polite installation admission was blocked by memory pressure.

Model: openai-codex/gpt-6.1-sol

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
@PsychedelicShayna PsychedelicShayna added bug Something isn't working priority: p1 High value or prerequisite for several issues ready-for-human Requires human implementation labels Nov 11, 2026
@github-actions github-actions Bot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:S labels Nov 11, 2026
Use a NeoCode executable and Debian package name so generated menu files and package ownership remain distinct from upstream T3 Code. Assert the packaging fields in the existing build-configuration test. No build or tests run by this worker.

Model: openai-codex/gpt-6.1-sol

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
@github-actions

Copy link
Copy Markdown

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for 4b033a5.

This comment will update automatically after the next completed run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working priority: p1 High value or prerequisite for several issues ready-for-human Requires human implementation size:S vouch:trusted PR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant