Documentation
Supported platforms and hosts
Understand Nightshift support across Cursor, Codex, Claude Code, macOS, Linux, native Windows, WSL, and remote environments.
Updated
Which coding hosts and operating systems does Nightshift support?
Nightshift ships native skills and hook wiring for Cursor, Codex, and Claude Code. macOS and Linux use the shell runtime; native Windows uses PowerShell. Remote setups work only when the host, plugin, project, and watchman share the same environment boundary.
Coding hosts
The package augments each host through its native plugin, skill, and hook surfaces instead of wrapping or proxying the runtime. The durable contract stays shared while recovery follows evidence each host actually exposes.
- Cursor: native skills and hooks, with conservative IDE-to-CLI recovery.
- Codex: skills, gates, guards, scheduling, and rollout-aware watchman.
- Claude Code: namespaced commands, hooks, scheduling, transcript signals, and watchman.
Operating systems
Use the runtime built for the environment actually executing the host.
- macOS: bundled shell runtime and launchd schedule generation.
- Linux: bundled shell runtime and cron schedule generation.
- Native Windows: PowerShell hooks, process checks, and Task Scheduler generation.
- WSL: Linux runtime; do not split components across Windows and the distribution.
Verified environment boundary
Remote SSH and devcontainer paths are verified when all runtime components are co-located. Nightshift does not claim support for a harness or split boundary it has not verified.
Start with a bounded prompt
This prompt names the outcome and preserves Nightshift’s review boundary. Paste it into the supported coding host from the project you want to change.
Check this host, shell, filesystem, project location, and coding host against Nightshift's supported platform boundaries before setup.What this workflow does not claim
- Native Windows is CI-verified on x64 with local fixtures; an authenticated desktop session remains an attended check.
- Split host/workspace environments and unsupported network filesystems are refused.
Evidence and sources
These links support the released behavior, public outcomes, or problem language described on this page.