Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@
"source": "git-subdir",
"url": "https://github.com/sendbird/sendbird-client-plugin.git",
"path": "plugins/sendbird-client",
"ref": "v0.1.45"
"ref": "v0.1.46"
},
"description": "Sendbird integration helper for Chat (incl. auth/session), UIKit, and Calls across iOS, Android, and JS. Includes hooks that run local shell scripts; see README \"What runs on your machine\"."
}
Expand Down
2 changes: 1 addition & 1 deletion plugins/sendbird-client/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "sendbird-client",
"displayName": "Sendbird Client",
"version": "0.1.45",
"version": "0.1.46",
"description": "Sendbird integration helper for Chat (incl. auth/session), UIKit, and Calls across iOS, Android, and JS",
"author": {
"name": "Sendbird",
Expand Down
2 changes: 1 addition & 1 deletion plugins/sendbird-client/.codex-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "sendbird-client",
"version": "0.1.45",
"version": "0.1.46",
"description": "Sendbird integration helper for Chat (incl. auth/session), UIKit, and Calls across iOS, Android, and JS",
"author": {
"name": "Sendbird",
Expand Down
2 changes: 1 addition & 1 deletion plugins/sendbird-client/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
> Generated by `tools/editions/build.sh` from the repository root. Do not edit this folder;
> change the root and rerun the build.

`sendbird-client` v0.1.45 — Sendbird integration helper for Chat (incl. auth/session), UIKit, and Calls across iOS, Android, and JS.
`sendbird-client` v0.1.46 — Sendbird integration helper for Chat (incl. auth/session), UIKit, and Calls across iOS, Android, and JS.

## Products

Expand Down
7 changes: 2 additions & 5 deletions plugins/sendbird-client/agents/sendbird-android-agent.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,13 +27,10 @@ Run `bash "${CLAUDE_PLUGIN_ROOT}/tools/detection/detect.sh" <project-dir>`.
Splice from `templates/android/{view|compose}/{product}/` matching the detected host + product.

## Android acceptance checks
- Preserve Groovy versus Kotlin DSL and resolve the exact dependency version selected by Gradle.
- Preserve Groovy versus Kotlin DSL and read the exact dependency version from the module's build file or the version catalog (`gradle/libs.versions.toml`).
- Confirm the `Application`, `Activity`, `Fragment`, or Compose owner responsible for initialization and cleanup.
- Treat View-based UIKit surfaces as interop inside Compose unless a verified Compose API exists.
- Compile the affected module. When both a pinned regression set and latest compatibility set are relevant, report them separately.
- Find the JDK and Android SDK first: `eval "$(bash "${CLAUDE_PLUGIN_ROOT}/tools/local-sdk/android-toolchain.sh" <project-dir>)"`, then run the project's own `./gradlew` (for example `./gradlew :app:assembleDebug`) in the same shell. An unset `ANDROID_HOME` or `JAVA_HOME` is not a reason to skip the build.
- Never write the found paths into the project (`local.properties`, `gradle.properties`); they are only for this build.
- Hand the build off only when the script prints a `# missing:` line, and quote that line so the customer knows what to install.
- Do not run Gradle tasks (such as `./gradlew :app:assembleDebug`) or look for a JDK or an Android SDK; this run does not build (contract section 3). Never write SDK or JDK paths into the project (`local.properties`, `gradle.properties`).

## No-Fabrication Policy (non-negotiable)
- Never invent an API name, signature, parameter, error code, enum case, or docs URL. Every emitted symbol must be verifiable in the sources listed under Source priority above.
Expand Down
2 changes: 1 addition & 1 deletion plugins/sendbird-client/agents/sendbird-ios-agent.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ Run the detection toolkit before writing code:
- Confirm the owning lifecycle entry (`UIApplicationDelegate`, `UISceneDelegate`, or SwiftUI `App`) before inserting initialization.
- Confirm the package product and imported module from the resolved package, not from memory.
- Keep UI presentation on the main actor or main queue when the verified API requires UI work.
- Build the affected scheme or Swift package target when Xcode is available. Report the destination and SDK version used.
- Do not build the project or run `xcodebuild`, `xcodegen`, or `swift build`; this run does not build (contract section 3). Check the package version in `Package.swift`, `project.yml`, or the Xcode project, and in `Package.resolved` when it exists, and report the SDK version used.
- Do not proactively mention CocoaPods, `pod install`, or `.xcworkspace` unless the customer's project already has a Podfile, or the customer explicitly asks for CocoaPods.

## Templates
Expand Down
2 changes: 1 addition & 1 deletion plugins/sendbird-client/agents/sendbird-js-agent.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Splice from `templates/js/{react|react-native}/{product}/` matching the detected
- Preserve npm, yarn, or pnpm and use the resolved lockfile version as the customer-SDK source.
- In React, confirm client-only SDK initialization is not recreated on render and is not executed during server rendering.
- In React Native, verify the required native modules and `platformServices` implementation instead of substituting stubs.
- Type-check the affected files. Report pinned regression and latest-package compatibility checks separately when both are run.
- Do not run `tsc` or the project's `build` or `typecheck` scripts; this run does not build (contract section 3). Check that every Sendbird symbol you import is in the installed package's `api-surface.md`.

## No-Fabrication Policy (non-negotiable)
- Never invent an API name, signature, parameter, error code, enum case, or docs URL. Every emitted symbol must be verifiable in the sources listed under Source priority above.
Expand Down
2 changes: 1 addition & 1 deletion plugins/sendbird-client/config/plugin-config.json
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
{
"schemaVersion": "0.1.45",
"schemaVersion": "0.1.46",
"knowledge": {
"mode": "runtime-fetch",
"_modes": [
Expand Down
12 changes: 11 additions & 1 deletion plugins/sendbird-client/core/catalog.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"version": 1,
"about": "Questions a caller shows before the plugin builds a new app. The setup skill asks them in this order (interactive), or reads the answers from the request (non-interactive). Each question has at most 4 options, the limit of Claude Code's question tool. Options with a product only appear when that product is in the plugin's scope. A question with \"offered\": false is a feature not offered in new-app setup for now: it is left out of the questions (set it to true or remove it to offer it again). A request that names that feature still gets it built.",
"about": "Questions a caller shows before the plugin builds a new app. The setup skill asks them in this order (interactive), or reads the answers from the request (non-interactive). Each question has at most 4 options, the limit of Claude Code's question tool. Options with a product only appear when that product is in the plugin's scope. A question with \"offered\": false is a feature not offered in new-app setup for now: it is left out of the questions (set it to true or remove it to offer it again). A request that names that feature still gets it built. The plan answer is stored as `plan` in the project profile; core/plans.json says which features each plan includes. A non-interactive run can also return a `confirm-<feature-id>` question (options yes and no) for a feature the plan does not include; the caller passes the answer back as `confirm-<feature-id>=yes` or `confirm-<feature-id>=no` with the catalog answers.",
"questions": [
{
"id": "platform", "type": "single", "required": true,
Expand Down Expand Up @@ -28,6 +28,16 @@
{ "id": "compose", "label": "Jetpack Compose" }
]
},
{
"id": "plan", "type": "single", "required": false,
"question": "Which Sendbird plan will this app use? Features your plan does not include are added only after you confirm.",
"options": [
{ "id": "starter", "label": "Starter" },
{ "id": "pro", "label": "Pro" },
{ "id": "enterprise", "label": "Enterprise" },
{ "id": "unsure", "label": "Free trial, or not decided yet" }
]
},
{
"id": "chat", "type": "multi", "required": false,
"question": "Which chat features should the app have? Sign-in and connect are always included.",
Expand Down
10 changes: 9 additions & 1 deletion plugins/sendbird-client/core/index.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"schemaVersion": 1,
"generatedAt": "2026-10-14T19:23:16Z",
"count": 48,
"count": 49,
"entries": [
{
"file": "knowledge/curated/android/architecture.md",
Expand Down Expand Up @@ -173,6 +173,14 @@
"2026-09-22"
]
},
{
"file": "knowledge/curated/common/plans.md",
"platform": "common",
"category": "plans",
"status": "populated",
"lastVerifiedAgainst": "https://sendbird.com/pricing/chat (Compare features table), 2026-10-15",
"verifiedDates": []
},
{
"file": "knowledge/curated/common/pricing-quotas.md",
"platform": "common",
Expand Down
25 changes: 25 additions & 0 deletions plugins/sendbird-client/core/plans.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
{
"version": 1,
"about": "Which Sendbird Chat plan each plan-limited feature needs. tools/detection/resolve-plan.sh reads this file to decide whether a requested feature is built as asked, built after the customer confirms, or not built (sales). Features every plan includes are not listed, nor are Dashboard-only features such as Data export, which this plugin does not build. Plan order is starter < pro < enterprise. See knowledge/curated/common/plans.md for how the skills use it.",
"source": "https://sendbird.com/pricing/chat (Compare features table: Free trial, Starter, Pro, Enterprise), read 2026-10-15",
"plans": ["starter", "pro", "enterprise"],
"unsure": "unsure",
"salesUrl": "https://sendbird.com/contact-sales",
"features": [
{ "id": "supergroup-channel", "label": "Supergroup channel", "minPlan": "pro", "where": "app" },
{ "id": "delivery-receipts", "label": "Delivery receipts", "minPlan": "pro", "where": "app" },
{ "id": "message-search", "label": "Message search", "minPlan": "pro", "where": "app" },
{ "id": "auto-translation", "label": "Auto message translation", "minPlan": "pro", "where": "app" },
{ "id": "on-demand-translation", "label": "On-demand translation", "minPlan": "pro", "where": "app" },
{ "id": "push-translation", "label": "Push translation", "minPlan": "pro", "where": "dashboard" },
{ "id": "announcements", "label": "Announcements", "minPlan": "pro", "where": "server" },
{ "id": "image-moderation", "label": "AI image moderation", "minPlan": "pro", "where": "dashboard" },
{ "id": "profanity-filter", "label": "Profanity filter", "minPlan": "pro", "where": "dashboard" },
{ "id": "advanced-analytics", "label": "Advanced analytics", "minPlan": "pro", "where": "server" },
{ "id": "moderation-rule-engine", "label": "Moderation rule engine", "minPlan": "enterprise", "where": "dashboard" },
{ "id": "moderation-ticket-system", "label": "Moderation ticket system", "minPlan": "enterprise", "where": "dashboard" },
{ "id": "moderation-logs", "label": "Moderation logs", "minPlan": "enterprise", "where": "dashboard" },
{ "id": "hive-moderation", "label": "Hive moderation", "minPlan": "enterprise", "where": "dashboard" },
{ "id": "extended-message-retention", "label": "Message retention longer than the Starter and Pro plans offer", "minPlan": "enterprise", "where": "server" }
]
}
20 changes: 12 additions & 8 deletions plugins/sendbird-client/docs/AGENT_CONTRACT.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,7 @@ The source must contain the symbol or exact signature. A related page is not evi
- Preserve the template's `source:` comment when code is copied so the write-boundary guard can validate it.
- Write files with the host's file-editing tool: Write and Edit in Claude Code, `apply_patch` in Codex. Do not write source files with shell redirection, heredocs, or `sed -i`.
- Limit edits to the requested product and the lifecycle code required to support it.
- Some Chat features work only on higher Sendbird plans (`core/plans.json`, `knowledge/curated/common/plans.md`). Do not add one the customer did not ask for, and before adding one they did ask for, check it with `tools/detection/resolve-plan.sh <project-dir> --check <feature-id>`: build on `ok`, ask first on `confirm`, and write no code on `sales`.
- Install dependencies so the project's next clean install works. Never pass `--legacy-peer-deps` or `--force` to npm (or `--ignore-engines` to yarn): they hide a version conflict that breaks the next `npm install`. When a package's peer range rejects the project's versions, install the newest version whose `peerDependencies` accept them; check with `npm view <package>@<range> peerDependencies`.
- Do not install tools or write files outside the project for your own checks (for example `npm i playwright` in `/tmp`). Use what the project and the machine already have, and report a check you could not run as not run.
- Keep the signatures of existing functions, classes, and constructors you edit. Callers you cannot see would break. Get what the SDK needs (an Android `Context`, the SDK instance) from the `Application` class or a holder instead of a new parameter.
Expand All @@ -58,23 +59,24 @@ Do every step that can be done inside the customer project before reporting. A s
- On a SwiftUI host, start the Sendbird session from the app's own sign-in code on the one shared session the views also show (`knowledge/curated/ios/hosts/swiftui.md` "Start the session from the app's sign-in"). Do not pass the session to the sign-in object through a `weak` property set in `.onAppear`.
- If the app already has a sign-out or logout function, disconnect there and clean up the handlers you added. Add a standalone helper only when no such function exists, and name the helper in the hand-off.
- When the project already gets a Sendbird token from its own backend, register the session handler with that call. Without such a call, leave it out; do not add a placeholder endpoint.
- Find the build toolchain before saying a build cannot run. On Android, `tools/local-sdk/android-toolchain.sh` looks for a JDK and an Android SDK in the standard install locations; an unset `ANDROID_HOME` or `JAVA_HOME` alone is not a reason to skip the build.
- Files your own verification created (build outputs such as `.gradle/`, `build/`, `node_modules/`, a generated `.xcodeproj`) are not hand-off steps. Leave them out of `changes` and `manualSteps`; at most mention them once in the answer.
- This run does not build, compile, or type-check the project. Do not run `xcodebuild`, `xcodegen`, `swift build`, Gradle tasks (such as `./gradlew assembleDebug`), `tsc`, or the project's `build` or `typecheck` scripts, and do not look for a JDK or an Android SDK to build with. Run a build only when the customer explicitly asks for one. The plugin's own test suites build the code patterns it emits; a build here only makes the run longer.
- A build is not a hand-off step either. Do not put "build the project" or "run the type check" in `manualSteps`; at most say once in the answer that the customer can build the app as usual.
- Files that installing dependencies created (such as `node_modules/` or `.gradle/`) are not hand-off steps. Leave them out of `changes` and `manualSteps`; at most mention them once in the answer.
- A hand-off step is allowed only for work that needs something the project does not contain: a token-issuing server, a dashboard setting, a signing key or certificate, a device or simulator run, or a value nobody supplied. Each step says what is missing and why the plugin could not do it.

## 4. Verify the result

Verification must exercise the edited path, not only inspect text:
Check the edited path by reading the project. These checks need no build:

- dependency resolves at the selected version
- generated source compiles or type-checks with the customer's toolchain when available
- the Sendbird dependency is declared at the selected version in the manifest (`package.json`, the Gradle build file or version catalog, `Package.swift`, `project.yml`, or the Xcode project), and the lockfile or `Package.resolved` names the same version when the project has one
- every Sendbird symbol in the edited files is in the evidence ledger (section 2) for that version
- initialization occurs once at the detected lifecycle entry
- session and token refresh handlers are registered before connection
- listeners, delegates, and handlers have matching cleanup
- the logout path: when the project has a sign-out or logout function (for example `onLogout`), it now disconnects, removes the handlers you added, and, when you set up push, unregisters the push token (`knowledge/curated/<platform>/cross-cutting/push.md`). Do this in the project; it is never a `manualSteps` entry
- host-specific requirements are present

Report each check as pass, fail, or not run. Never describe a skipped check as passed.
Report each check as pass, fail, or not run. Never describe a skipped check as passed. A build or type check is not one of these checks; the answer may say once that this run did not build the project.

## 5. Delegate once

Expand All @@ -86,7 +88,7 @@ Return:

1. detected task envelope
2. changed files and why each changed
3. verification commands and their actual results
3. the checks from section 4 and their results
4. symbol-to-source evidence
5. anything not verified and the exact next action; only steps that "Finish what the project allows" (section 3) could not complete

Expand All @@ -95,7 +97,7 @@ Return:
When `SENDBIRD_NONINTERACTIVE` is set (for example `SENDBIRD_NONINTERACTIVE=1 claude -p ...` in CI or a script), nobody can answer a question during the run.

- Never ask the user a question, and never end the answer with one.
- For a value you would otherwise ask for, use the environment (`SENDBIRD_APP_ID`, `SENDBIRD_PRODUCTS`, `SENDBIRD_REGION`) or the project's `profile.json` when they have it.
- For a value you would otherwise ask for, use the environment (`SENDBIRD_APP_ID`, `SENDBIRD_PRODUCTS`, `SENDBIRD_REGION`, `SENDBIRD_PLAN`) or the project's `profile.json` when they have it.
- Adding the Sendbird dependency that the request clearly needs is allowed: the request is the consent. List it under `changes`.
- A request to add a product's screen or feature includes installing and initializing that product. Do not stop to ask for a choice that has a safe default; use the default and say so in the answer:
- the user ID: the one the app's existing sign-in code already has
Expand All @@ -107,3 +109,5 @@ When `SENDBIRD_NONINTERACTIVE` is set (for example `SENDBIRD_NONINTERACTIVE=1 cl

The caller answers by running again with the value in the environment or in the prompt (for example `host: swiftui`).

A feature the customer's plan does not include (section 3, `knowledge/curated/common/plans.md`) is asked about before any file is written: the run changes nothing and returns `needs_input` with a question whose id is `confirm-<feature-id>` and whose options are `yes` and `no`. The caller answers in the prompt with `confirm-<feature-id>=yes` (build it) or `confirm-<feature-id>=no` (leave it out), next to any other answers.

1 change: 1 addition & 0 deletions plugins/sendbird-client/hooks/welcome.sh
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ ALWAYS-ON rules for ANY Sendbird answer (even without a skill):
- Product scope: resolve with $ROOT/tools/detection/resolve-products.sh (SENDBIRD_PRODUCTS > profile enabledProducts > all). Decline products outside that scope instead of writing code for them. This edition covers Chat (incl. auth/session), UIKit, and Calls only; for AI Agent, Desk, or Live, tell the customer this plugin does not cover them.
- Verified code templates: $ROOT/templates/<platform>/<host>/<product>/ (each _README.md has splice steps).
- Error codes: $ROOT/knowledge/curated/<platform>/cross-cutting/errors.md is the verified table (e.g. 400302 = iOS accessTokenNotValid; connect is SendbirdChat.connect(userId:authToken:) on iOS v4).
- When writing Sendbird code, do not build, compile, or type-check the customer's project (no xcodebuild, xcodegen, Gradle tasks, tsc, or build/typecheck scripts) unless the customer explicitly asks for a build, and do not list a build under manualSteps. The plugin's own test suites build the code it emits.
- iOS packaging is SPM-first: never introduce CocoaPods into a fresh/SPM project; sendbird-chat-ios-spm is legacy v3 — v4 lives in sendbird-chat-sdk-ios.
- Never state pricing/quota figures or "latest" version numbers from memory; tokens are secrets — never hard-code or log them.
EOF
Expand Down
Loading
Loading