Skip to content

api: drop the /v1 prefix from every route - #103

Merged
hbrooks merged 1 commit into
mainfrom
remove-v1-prefix
Aug 9, 2026
Merged

api: drop the /v1 prefix from every route#103
hbrooks merged 1 commit into
mainfrom
remove-v1-prefix

Conversation

@hbrooks

@hbrooks hbrooks commented Aug 9, 2026

Copy link
Copy Markdown
Member

The backend removed the /v1 prefix from the public API routes (ellipsis-dev/ellipsis#6166): everything now answers at /sessions, /reviews, /models, and so on. This PR updates every path the CLI builds to match.

What changed

  • Request paths: all REST paths in src/lib/api.ts and the WebSocket stream URL in src/lib/stream.ts.
  • Help text: the apiRoutes(...) route lines in every command file, which show in --help.
  • Tests: expected URLs in the api/stream/discovery/output/search suites.
  • Docs and skills: README, docs/RUN_STREAMING_SPEC.md, both skills, and the smoke scripts. Prose like "the /v1 host" became "the API host" rather than leaving a dangling slash.

The one v1 left behind is a comment naming the mono repo file ellipsis/src/public_api/routers/v1/v1_router.py, which is a real path, not a route. Config-file version: v1 YAML and the v1 -> v2 config migration are unrelated and untouched.

Verification

tsc --noEmit is clean and all 435 tests pass (24 files).

Follow-ups (not in this PR)

  • Bump @ellipsis-dev/sdk to ^0.6.0 once the regenerated SDK is published from the mono repo (the CLI only imports types and stream machinery from it, so it works on 0.5.0, but 0.5.0's EllipsisClient and paths type still spell /v1).
  • Released binaries hardcode /v1: the backend deploy needs to keep answering the old paths (or we accept breaking pre-release binaries) until users upgrade.

Important

Removes the /v1 prefix from all API routes in the CLI to match the backend's updated public API.

  • REST API calls in src/lib/api.ts and WebSocket stream URL in src/lib/stream.ts now use routes without the prefix (e.g., POST /sessions instead of POST /v1/sessions).
  • Route paths shown in command help text (apiRoutes(...) calls across all command files) updated accordingly.
  • Expected URLs in api/stream/discovery/output/search test suites updated.
  • Documentation and help text changed "the /v1 API" to "the public API" or "the API" throughout README, spec docs, and smoke scripts (but left intact: the monorepo file path ellipsis/src/public_api/routers/v1/v1_router.py, config migration comments about v1→v2).
  • TypeScript compiles cleanly and all 435 tests pass.

This description was created by Ellipsis for ff1d31c. It will automatically update as commits are pushed.

The backend removed the /v1 prefix from the public API routes
(ellipsis-dev/ellipsis#6166): everything now answers at /sessions,
/reviews, /models, etc. Update every path the CLI builds - the REST
client, the WebSocket stream URL, the apiRoutes help lines - plus the
tests, docs, skills, and smoke scripts that spell out routes.

The one v1 left behind is a comment pointing at the mono repo file
ellipsis/src/public_api/routers/v1/v1_router.py, which is a real path,
not a route. Config-file 'version: v1' YAML and the v1->v2 config
migration are unrelated and untouched.

Still pending separately: bump @ellipsis-dev/sdk once 0.6.0 (with the
regenerated prefix-free paths) is published from the mono repo.
@hbrooks
hbrooks merged commit bf0646e into main Aug 9, 2026
1 check passed

@ellipsis-dev ellipsis-dev Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

Looks good to me! 👍

Reviewed ff1d31c in 3 minutes, 35 seconds.
  • Reviewed 1 commit with 1359 lines of code in 38 files
  • Ran 1 review agent producing 0 comments where 0 were posted
  • This pipeline runs no gatekeeper, so findings are posted as written.
  • View full details on ellipsis.dev

This review was created by Ellipsis. You can tag @ellipsis in this pull request.

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