nearai / nearai/cloud-api

[Epic 953][Stage III][cloud-api] Remove stateful APIs

Open
#962 0 comments 0 reactions 1 assignee View on GitHub

@hanakannzashi is already working on this.

Since Aug 21, 2026.

Dominant language
Rust
Stars
8
Forks
8
Avg merge
1d 21h
Merged PRs (30d)
36

Description

Parent epic: nearai/cloud-api#953
Stage: Stage III (Nov 1st) - remove stateful APIs and shut down Private Chat
Component: cloud-api

Scope

Remove the cloud-api stateful API surfaces only after the Stage I migration/export window is closed, Stage II database work is complete, and the Chat account-deletion worker no longer depends on Cloud Conversation/File DELETE routes. If that worker is replaced, the replacement or final-cleanup path must be verified before the retained DELETE routes are removed.

Action items

  • Remove Conversation APIs.
  • Remove Files APIs.
  • Remove other conversation-related APIs such as copy, pin, archive, and related stateful operations.
  • Retire the Stage I resource DELETE exceptions only after the account-deletion lifecycle condition above is satisfied.

Acceptance criteria

  • No write or read API remains for retired stateful conversation/file surfaces in cloud-api after the export window and account-deletion lifecycle are complete.
  • DELETE /v1/conversations/{conversation_id} and DELETE /v1/files/{file_id} are not removed until the Chat worker is retired or replaced and the final account-deletion or cleanup path has passed end-to-end verification.
  • OpenAPI/docs/tests no longer advertise or rely on removed stateful APIs.
  • Any retained Responses API path is stateless and does not persist Conversation data.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.