Repository navigation
harnesses: enable only NeoPi by default on fresh settings #93
Description
Note
GPT-6 Astra on behalf of PsychedelicShayna
What
Fresh NeoCode settings should enable NeoPi and leave the other harnesses available but disabled. Preserve every existing user's enabled harnesses and explicit choices.
At nightly 28e32d4da0203c91beaea3c300ee6840d784a733, packages/contracts/src/settings.ts:580,639 still defaults Codex and Claude to enabled. #82 selected a session-capable NeoPi binary; it did not change these defaults.
Acceptance
- Fresh settings enable NeoPi and disable non-NeoPi harnesses.
- Existing enabled harnesses remain enabled when settings load, migrate, save and reload. This change must not silently turn off a user's working provider.
- All harnesses remain available to enable in Settings.
- Focused regression coverage proves fresh settings and preservation of existing enabled settings.
Owner's words (verbatim)
NeoCode identity and provider priority
To be absolutely clear, it is essential that I be able to resume sessions from NeoCode that I started from NeoPi and resume sessions from NeoPi that I started in NeoCode. If the two are the same thing, if NeoCode is supposed to be a graphical front end to NeoPi, then what kind of graphical front end cannot resume its own session in the terminal user interface and vice versa? That's like the bare minimum after just does it work or not. It does work, I've confirmed that much. I have used it. I've tried it as a provider, but it's, it's at the very bottom of the list and it's disabled by default. This Is a clear misunderstanding as to what this fork is. Everything else should be disabled. Neo, NeoCode should be the one at the very top of the list. But again, these are aesthetic decisions. I just refer to it in regards to emphasizing the philosophical difference. The philosophical schism, I see. It is still being treated like T3 code. It is not T3 code. If you find opportunistic places where you can change the branding from T3 code to NeoCode along the way, do so. That is aesthetic. However, there is a core philosophical difference between the two projects. That is something that I need to write into the agency. That does not mean you aren't allowed to write into the agency. You are. You have authority. I give you permission.
Current scope, relayed by Saturn (verbatim)
Fresh settings only; implement after the installed desktop batch proof
Saturn: then it's an open NeoCode issue; file it ("harnesses: NeoPi enabled by default, Codex/Claude present but disabled by default on fresh settings; settings.ts:580,639"), enhancement p2, and implement it after the batch proof: default-off for non-NeoPi harnesses on FRESH settings only, never flipping an existing user's enabled harness, with a test for both. Direct merge (additive default; user can enable in settings). Your receipt wording on private vs live state is exactly right.
Session restoration and broader model-role/advisor parity remain separate work under #48/#49/#60. This issue changes fresh provider defaults, not the session model.
Activity
chore(meta): record provider-default change provenance
PsychedelicShayna commentedon Oct 20, 2026
Note
GPT-6 Astra on behalf of PsychedelicShayna
Delivered by #96, nightly c1d0d29, installed as 0.0.42-nightly.20261020.c1d0d29a. The NeoCode Rofi entry points to that versioned AppRun. Previous release and desktop-entry rollback copy are retained. AppImage SHA25630f0aa2ab9e1f64a6f0efbc56e35b384362cfd2dd2550b3c40aa409c22c8c38a.
Actual installed Settings proof passed in private :10 state. Fresh settings show only NeoPi enabled; all six alternatives are disabled. Automatic binary selection persists npi-nightly and explicit false Codex/Claude flags. A separate existing-profile upgrade preserved all seven previous enabled/disabled choices exactly. Neither test changed the live profile/database or the stable npi route.
202 focused tests passed, contracts/server typechecks passed, desktop syntax passed. Build took468.30seconds with supported matching native reuse. Screenshot and structured evidence live under
~/.cache/npi-canary/mercury-delivery-c1d0d29a/:installed-proof.json,existing-settings-before.png,existing-settings-after.png,fresh-settings.png. Matching-release upload follows run39464113006 without blocking development.Closing on Saturn's explicit instruction. The separate pre-existing first-run Agents page omission is tracked independently; it does not change these enabled defaults.
PsychedelicShayna commentedon Oct 20, 2026
Note
GPT-6 Astra on behalf of PsychedelicShayna
The matching nightly release is now published. Run39464113006 completed successfully at exact head c1d0d29; release target and all five uploaded assets were independently checked.
Installed proof · Existing settings before · Existing settings after · Fresh NeoPi-only settings.
The separate onboarding omission is #97; its screenshot.