Skip to content

Remove legacy Code Everywhere remote inbox HTTP path#23

Merged
cbusillo merged 1 commit intolocal/cbusillo-overlayfrom
chore/remove-code-everywhere-remote-path
May 4, 2026
Merged

Remove legacy Code Everywhere remote inbox HTTP path#23
cbusillo merged 1 commit intolocal/cbusillo-overlayfrom
chore/remove-code-everywhere-remote-path

Conversation

@cbusillo
Copy link
Copy Markdown
Owner

@cbusillo cbusillo commented May 4, 2026

Summary

  • remove the archived Code Everywhere HTTP polling adapter from the TUI remote inbox client
  • keep the active Every Code / Discord WebSocket bridge path and timeline fanout
  • preserve legacy remote_inbox.code_everywhere_url configs and CLI overrides only when they point at a WebSocket bridge URL; legacy HTTP polling URLs now warn and do not silently pretend to work
  • update repo workflow metadata away from Code Everywhere wording

Refs #19

Note: the non-runtime chatwidget smoke-helper rename was intentionally left out of this PR because touching code-rs/tui/src/chatwidget.rs trips the repo blob-size policy. The runtime remote inbox cleanup, explicit HTTP retirement behavior, and WebSocket compatibility path are covered here.

Validation

  • ./build-fast.sh
  • just local-code-rebuild
  • local DUI bridge smoke with remote_inbox.bridge_url: hello, heartbeat, command_ack, returncode 0
  • local DUI bridge smoke with legacy remote_inbox.code_everywhere_url using ws://: hello, heartbeat, command_ack, returncode 0
  • cd /Users/cbusillo/Developer/discord-blue && uv run python -m unittest tests.test_every_code

@cbusillo cbusillo force-pushed the chore/remove-code-everywhere-remote-path branch from 92beeb7 to 1a6950a Compare May 4, 2026 14:58
@cbusillo cbusillo force-pushed the chore/remove-code-everywhere-remote-path branch from 1a6950a to f1ae299 Compare May 4, 2026 15:10
@cbusillo cbusillo merged commit 3e95dba into local/cbusillo-overlay May 4, 2026
1 check passed
@cbusillo cbusillo deleted the chore/remove-code-everywhere-remote-path branch May 4, 2026 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant