Problem
cbusillo/code-everywhere has been archived/discontinued, but the active code repo still carries legacy Code Everywhere-specific names and possibly a legacy endpoint adapter inside otherwise useful remote UI/session-control infrastructure.
This should not become a broad deletion pass. The Discord bridge and the generic capabilities it depends on should stay. The goal is to separate reusable Every Code remote-control primitives from archived Code Everywhere product baggage.
Current evidence:
code-rs/core/src/config.rs still exposes remote_inbox.code_everywhere_url alongside the current bridge_url.
code-rs/tui/src/remote_inbox/client.rs still spawns spawn_code_everywhere_http_client(...) when code_everywhere_url is configured.
- The same client contains
CodeEverywhereHttpClient, CodeEverywhereCommand, code_everywhere_* mappers, polling, snapshot, command-claim, and command-outcome code.
- Several runtime/log/user-visible strings still say
Code Everywhere, including command issued_by values.
code-rs/tui/src/chatwidget.rs has Code Everywhere smoke helper names and prompt text.
- Tests still cover the Code Everywhere HTTP path and naming.
The current Discord integration lives in the active discord-blue repo and should not be confused with the archived code-everywhere project. The surviving integration and reusable remote UI capabilities should be preserved under current Every Code / remote inbox naming.
Keep
Preserve generic features that are useful for Discord today and for future UI/DUI surfaces, including:
- remote session hello/presence/status snapshots
- timeline/status fanout
- command claim/ack/reject semantics when still useful outside the archived service
- remote reply, continue, pause, new-session, end-session, approval, and
request_user_input plumbing
- host identity/label support
- tests that prove the generic remote-control protocol still works
Expected outcome
Audit the legacy Code Everywhere support and make a deliberate split:
- Keep the active Every Code remote inbox / Discord bridge behavior working.
- Keep generic remote UI/session-control primitives that could support a future UI we love or a broader DUI.
- Remove the discontinued
code_everywhere_url HTTP compatibility path only if no active or planned surface still needs that exact adapter.
- Rename reusable
CodeEverywhere* types/functions/tests/smoke helpers to current EveryCode, RemoteInbox, or similarly neutral names.
- Replace user-visible/log/issued-by strings that still say
Code Everywhere with current Every Code or neutral remote inbox wording.
- If the legacy HTTP compatibility path should remain temporarily, document its current owner, endpoint, and retirement criteria so it is not mistaken for the archived project.
Validation
- Existing remote inbox tests pass.
- Active Discord bridge/manual control flow remains compatible.
- Generic remote-control behavior remains available for future UI/DUI expansion.
- Config docs/tests no longer advertise a discontinued
code_everywhere_url path unless it is explicitly retained as temporary compatibility.
Related context
Problem
cbusillo/code-everywherehas been archived/discontinued, but the activecoderepo still carries legacy Code Everywhere-specific names and possibly a legacy endpoint adapter inside otherwise useful remote UI/session-control infrastructure.This should not become a broad deletion pass. The Discord bridge and the generic capabilities it depends on should stay. The goal is to separate reusable Every Code remote-control primitives from archived Code Everywhere product baggage.
Current evidence:
code-rs/core/src/config.rsstill exposesremote_inbox.code_everywhere_urlalongside the currentbridge_url.code-rs/tui/src/remote_inbox/client.rsstill spawnsspawn_code_everywhere_http_client(...)whencode_everywhere_urlis configured.CodeEverywhereHttpClient,CodeEverywhereCommand,code_everywhere_*mappers, polling, snapshot, command-claim, and command-outcome code.Code Everywhere, including commandissued_byvalues.code-rs/tui/src/chatwidget.rshas Code Everywhere smoke helper names and prompt text.The current Discord integration lives in the active
discord-bluerepo and should not be confused with the archivedcode-everywhereproject. The surviving integration and reusable remote UI capabilities should be preserved under current Every Code / remote inbox naming.Keep
Preserve generic features that are useful for Discord today and for future UI/DUI surfaces, including:
request_user_inputplumbingExpected outcome
Audit the legacy Code Everywhere support and make a deliberate split:
code_everywhere_urlHTTP compatibility path only if no active or planned surface still needs that exact adapter.CodeEverywhere*types/functions/tests/smoke helpers to currentEveryCode,RemoteInbox, or similarly neutral names.Code Everywherewith currentEvery Codeor neutralremote inboxwording.Validation
code_everywhere_urlpath unless it is explicitly retained as temporary compatibility.Related context
cbusillo/code-everywhereis archived and has no open issues after discontinuation cleanup.discord-blueissues fix(tui/limits): refresh expired reset windows over HTTP #28 and Detached tmux Every Code sessions do not register with DUI until attach #29 track active Every Code Discord control behavior, not the archived Code Everywhere repo.