菜单
Use when migrating an app onto the KurrentDB gRPC client from a legacy EventStoreDB client. Covers both the TCP rewrite and gRPC rebrand paths, plus the esdb to kurrentdb connection-string switch. NOT for code already on the KurrentDB client (use kurrent-docs) or server upgrades.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | kurrent-upgrade |
| description | Use when migrating an app onto the KurrentDB gRPC client from a legacy EventStoreDB client. Covers both the TCP rewrite and gRPC rebrand paths, plus the esdb to kurrentdb connection-string switch. NOT for code already on the KurrentDB client (use kurrent-docs) or server upgrades. |
Two flavours of migration land here, both targeting KurrentDB.Client / KurrentDBClient:
EventStore.Client 23.x and equivalents). A mechanical package + symbol rename plus a small number of API breaks.Pick the flavour first, then the language reference. Each reference is self-contained and walks the migration top-to-bottom.
| Source state | Flavour | Folder |
|---|---|---|
Legacy TCP client (.NET EventStore.ClientAPI / EventStoreConnection, JVM com.geteventstore:eventstore-client / EsConnection) | TCP rewrite | references/tcp-to-grpc/ |
Intermediate gRPC client (EventStore.Client 23.x, EventStore.Client.Grpc.*, com.eventstore:db-client-java, @eventstore/db-client, etc.) | gRPC rebrand | references/rebrand/ |
Already on KurrentDB.Client and kurrentdb:// | none | route to kurrent-docs |
If you cannot tell which flavour applies, run kurrentdb-client-detection first and use its classification.
| Language | TCP rewrite | gRPC rebrand |
|---|---|---|
| .NET | references/tcp-to-grpc/dotnet.md | references/rebrand/dotnet.md |
| JVM (Java) | references/tcp-to-grpc/jvm.md | references/rebrand/java.md |
| Node.js | (not authored) | references/rebrand/nodejs.md |
| Go | (not authored) | references/rebrand/go.md |
| Python | (not authored) | references/rebrand/python.md |
| Rust | (not authored) | references/rebrand/rust.md |
The TCP JVM reference targets Java consumers of EventStore.JVM (the Scala-based legacy client exposes a Java facade under eventstore.j.*); pure Scala consumers follow the same API mapping but keep scala.concurrent.Future instead of CompletableFuture.
For an ecosystem and flavour combination not in the table, link the official client upgrade docs and do not improvise package names, connection strings, or API shapes. The shape of these renames is not portable across SDKs.
Done-criteria. Every TCP-rewrite reference opens with a
## Required outcomeschecklist. Load it first, satisfy each item, and reread before declaring the migration complete. The rebrand references close with an equivalent end-of-page checklist.
KurrentDB.Client. Use kurrent-docs.kurrent-upgrade-v*-to-v* skills.kurrent-docs.references/grpc-retry-policy.md. The gRPC client has no built-in retries; wire a retry pipeline before declaring done. The file holds the language-neutral contract and a .NET recipe (Polly v8); other languages apply the contract to their idiomatic resilience library. For the rebrand flavour this is only relevant if the project does not already have retry policies wired (the retry contract did not change in the rebrand).Use when the user is working with KurrentDB, from writing application code against the client SDKs to operating the self-hosted server or running on Kurrent Cloud.
Use when installing, configuring, or operating the kcap CLI, aka the Kurrent Capacitor CLI / Capacitor CLI (npm @kurrent/kcap), which records Claude Code, Codex, and Cursor sessions to a Capacitor server. Covers install/setup/login, profiles, where its config and on-disk state live, importing and remapping past sessions, recap/eval/errors on a recorded session, visibility and privacy (hide, disable, ignoring or excluding repos and directory trees from recording), the daemon and hosted agents, MCP sessions/review and PR review, and plugin hooks.
Use when inventorying an application's KurrentDB or EventStoreDB client surface before a migration or audit. NOT for server or cluster state (use kurrentdb-server-detection).
Use when working on, updating, or reviewing code that instantiates or configures a KurrentDB gRPC client across the supported SDKs. Covers connection-string parameters, single-node versus gossip discovery for clusters, node preference for read and write splits, HTTP/2 keepalive for long-lived connections behind NAT or load balancers, default deadlines, serverless client reuse, and triage of connection-related failures like discovery timeouts, deadline exceeded, keep-alive resets, and TLS verification errors. Do NOT use for authentication mechanics, certificate provisioning on the server, EventStoreDB to KurrentDB migration, or server-side cluster sizing.
Use when inventorying a deployed KurrentDB or EventStoreDB server for its version, cluster topology, license status, and deployment method by reading runtime endpoints, deployment manifests, and on-disk version banners. NOT for client SDK state (use kurrentdb-client-detection), Kurrent Cloud projects, or migration execution.