Skip to content

fix: Align API contract with LibreChat client (storage_session_id, kind, resource fields)#110

Merged
usnavy13 merged 3 commits into
mainfrom
dev
May 13, 2026
Merged

fix: Align API contract with LibreChat client (storage_session_id, kind, resource fields)#110
usnavy13 merged 3 commits into
mainfrom
dev

Conversation

@usnavy13
Copy link
Copy Markdown
Owner

Summary

Promotes dev → main. Contains the contract alignment changes from #109:

  • storage_session_id alias across all file-related responses and request models
  • kind=skill/kind=agent recognition in batch upload for skill-priming (supersedes fix: recognize kind field for skill priming, add storage_session_id #108)
  • resource_id, kind, version fields on FileRef, RequestFile, and PTCFileInput models
  • kind/id/version query params on GET /files/{session_id} for scoped listing

Test plan

  • 505 unit tests, 239 integration tests, 86 functional tests passing
  • All CI checks passing (flake8, black, mypy)
  • Verified on live HTTPS endpoint + LibreChat GUI
  • Docker logs clean

🤖 Generated with Claude Code

usnavy13 and others added 3 commits May 8, 2026 23:12
Updated the API responses and models to replace all instances of session_id with storage_session_id for consistency. This change includes updates to the upload, list, and batch file operations, as well as adjustments in the corresponding tests and documentation to reflect the new naming convention.
…support

Updated the upload_files_batch and list_files functions to include support for resource kind and version parameters. The upload logic now marks files as agent files based on the kind provided. Additionally, the RequestFile and FileRef models have been updated to accept resource_id, kind, and version fields, with corresponding tests added to validate these changes.
fix: Align API contract with LibreChat client (storage_session_id, kind, resource fields)
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