Defined in cli/commands/neon.ts.

ds neon <neonctl arguments>
ds neon api <route>

Runs Neon's command-line tool, neonctl, with the team's shared organisation key, NEON_API_KEY, from the agent credentials file, and DevStride's Neon organisation: never a person's own neonctl sign-in. The key reaches staging and production alike (owner decision, 2026-10-05). Needs no AWS login and no stage bind.

  • Name the project on every command with --project-id. ds neon refuses init (which always uses a person's own sign-in) and link, checkout and set-context, because every session on the machine shares ds neon and a saved project would steer them all.
  • It runs neonctl from a private folder of its own (~/.config/devstride/neon), so a person's saved sign-in is never touched, and anything neonctl writes (a project link, an .env with a database password) stays out of every checkout.
  • ds neon api <route> reaches any Neon API route.

Until an admin has created the key and stored it (pbpaste | ds secrets set agent NEON_API_KEY, then ds secrets pull), the command refuses and says how; ds neon --help and ds neon --version still run. Setup's stage step needs the same key. The key is never shown in the command's output or errors. Credentials and access has every key's source.