Skip to content

Latest commit

 

History

History
28 lines (16 loc) · 1.45 KB

File metadata and controls

28 lines (16 loc) · 1.45 KB

CastCodes FAQ

What is CastCodes?

CastCodes is an open-source terminal and code workspace fork focused on local terminal and code workflows. The first rebrand pass changes external product identity while intentionally leaving many internal Rust crate/module names unchanged.

Is CastCodes connected to upstream services?

No. The public CastCodes build is local-only by default. It does not include sign-in, hosted telemetry, hosted crash reporting, billing, shared sessions, upstream release feeds, or upstream feedback flows. Feedback links route to this fork's GitHub issue tracker.

Why do internal names still say warp?

This pass avoids a risky blind rename. Internal names such as warp_core, warpui, warp_terminal, inherited upstream dependencies, protocol names, tests, and historical references may remain until a later internal rename.

Where does CastCodes store local data?

New public CastCodes builds write to CastCodes paths such as .cast-codes, Linux cast-codes, Windows castcodes\\CastCodes, and macOS dev.castcodes.CastCodes. Legacy upstream paths are only compatibility references and should not receive newly-created CastCodes data.

What should I run before opening a PR?

Run the most relevant checks for your change. For rebrand-facing changes, start with:

./script/check_rebrand
cargo check -p warp --bin cast-codes --features gui

If you touch path or channel identity code, also run the focused warp_core tests.