kevchess15/deepseek-harness
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
deepseek-harness/packages/api
History
imccyu 211e6939e3 Revert "Merge pull request #2698 from deepseek-harness/xtr/session-format-migration" 
This reverts commit 4b592eb90df20dc53dd12215921d5a9137214777, reversing
changes made to d15d3275d905e4d21229cd70a074388a428189d1.
2026-08-25 15:30:10 +08:00
..
gateway test(web): keep credential fixtures package-local 2026-08-25 14:23:47 +08:00
remotes fix(web): keep browser authentication synchronous 2026-08-25 14:23:47 +08:00
session-controller Revert "Merge pull request #2698 from deepseek-harness/xtr/session-format-migration" 2026-08-25 15:30:10 +08:00
workspace-controller refactor(client): remove compatibility imports 2026-08-23 23:06:38 +08:00
README.i18n.yaml docs(i18n): localize Chinese internal links 2026-08-18 19:00:37 +08:00
README.md refactor: apply repository naming contract 2026-08-13 00:54:38 +08:00
README.zh.md docs(i18n): localize Chinese internal links 2026-08-18 19:00:37 +08:00

README.md

api/ — Remote API layers

English | 中文

The application-facing Remote stack. remotes owns BFF policy and the selected business API, while gateway implements the Typert unary RPC endpoints shared by Host and Client environments.

Package Role ctx key
remotes/ Host Agent/Session lookup policy and Client Remote contribution assembly no service; configures ctx.typert and consumes ctx.remote
gateway/ Host Typert dispatcher and Client Remote endpoint ctx.typertGateway / ctx.remote

The runtime dependency direction is remotes → gateway → connection → webserver: the BFF consumes the shared TypertClientRemote contract, Gateway delegates transport to Connection, and Connection mounts on the HTTP server. Cordis service injection and Client module metadata preserve this order without importing the concrete Gateway from the Remotes Client entry.

Known Limitations and Deferred Work

  • Connection and WebServer remain at client/connection and host/webserver; a later package-only move can place them under api/connection and api/webserver without changing their service contracts.
  • The legacy API Proxy remains at host/apiproxy as the fallback for methods not yet migrated to Remote. It consumes the Host resolver owned by api-remotes so migrated and legacy methods retain one Agent/Session identity policy.