@takara-ai/miru-code 1.10.1 → 1.11.0

package/README.md

@@ -48,6 +48,7 @@ Plugin installs don't carry full CLI parity — what each one gives you depends
 | `miru` / Caveman / STE skills | ✅ | ✅ | ✅ |
 | Dedicated sub-agent (`miru:miru-code`) | ✅ | — | — |
 | Benchmark mode toggle (`/plugin configure`) | ✅ | — | — |
+| Self-hosted SageMaker embeddings (`/plugin configure`) | ✅ | — | — |
 | Credentials | own plugin-scoped dir | own plugin-scoped dir | n/a |
 
 `—` means the IDE's plugin schema has no equivalent mechanism to port these to (not a packaging gap we can close): Codex's and Cursor's plugin manifests have no `agents` or `userConfig` fields, so the dedicated sub-agent and the benchmark toggle are Claude-Code-only.
@@ -323,7 +324,7 @@ Miru sends **file contents** to the [Takara inference API](https://takara.ai) wh
 
 If you index proprietary code, make sure that sending snippets to Takara's endpoint fits your security and compliance requirements. `MIRU_WORKSPACE_ROOT` is an opt-in boundary for MCP local `repo` paths only, and restricts indexing to a single workspace directory when set.
 
-Enterprise self-hosted embeddings (no Takara egress): see [docs/self-hosted-sagemaker.md](docs/self-hosted-sagemaker.md).
+Enterprise self-hosted embeddings (no Takara egress): see [docs/self-hosted-sagemaker.md](docs/self-hosted-sagemaker.md), including the [Claude Code plugin settings](docs/self-hosted-sagemaker.md#claude-code-plugin).
 
 ## Benchmark mode
 

package/docs/self-hosted-sagemaker.md

@@ -174,6 +174,28 @@ After that, indexing and search embed via SageMaker — no egress to `infer.taka
 
 If `TAKARA_API_KEY` is still set in your shell or `.env.local`, remove it there too so it cannot conflict later.
 
+### Claude Code plugin
+
+The plugin has no terminal step. Do steps 1–3 first, then set the plugin settings. Run `/plugin`, open **miru**, and set:
+
+| Setting                  | Value                                                                                  |
+| ------------------------ | ---------------------------------------------------------------------------------------- |
+| `SageMaker endpoint ARN` | The `EndpointArn` output from step 2                                                     |
+| `AWS profile`            | The profile from step 3. It must already exist in `~/.aws`; Miru never creates one.       |
+
+Or from a shell, then restart Claude Code:
+
+```bash
+echo '{"sagemaker_endpoint_arn":"arn:aws:sagemaker:<region>:<account-id>:endpoint/<name>","aws_profile":"miru"}' \
+  | claude plugin configure miru@miru --values-stdin
+```
+
+When the ARN is set, it **takes priority over any stored Takara sign-in** and Miru does not contact `infer.takara.ai`. Nothing is deleted, so clearing the ARN returns you to Takara. Leaving the ARN blank means Takara is used. The profile is only read when an ARN is set.
+
+If the profile uses SSO, run `aws sso login --profile <name>` again whenever the token expires.
+
+The plugin's `auth` tool only handles Takara sign-in; SageMaker is configured through these settings only.
+
 ## Switch back to Takara
 
 ```bash
@@ -184,6 +206,8 @@ Enter your Takara API key. Setup validates it, saves it, and **deletes any store
 
 Also unset any `MIRU_SAGEMAKER_*` variables if you set them in the environment or `.env.local`.
 
+In the Claude Code plugin, clear the **SageMaker endpoint ARN** setting and restart.
+
 ## Environment alternatives
 
 Prefer `miru setup --sagemaker` so auth is checked automatically. You can also set:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@takara-ai/miru-code",
-  "version": "1.10.1",
+  "version": "1.11.0",
   "mcpName": "ai.takara/miru",
   "description": "Miru (見る) — hybrid code search for agents. Bun, TypeScript, Takara embeddings.",
   "type": "module",

package/src/credentials.ts

@@ -116,6 +116,32 @@ function clearTakaraEnv(): void {
   delete process.env.TAKARA_API_KEY;
 }
 
+/** A plugin `userConfig` value, or undefined when blank or left as an unsubstituted `${...}`. */
+function pluginConfigValue(name: string): string | undefined {
+  const value = process.env[name]?.trim();
+  return value && !isUnsubstitutedPlaceholder(value) ? value : undefined;
+}
+
+/**
+ * Plugin settings (`sagemaker_endpoint_arn` / `aws_profile` in plugin.json) arrive as
+ * MIRU_PLUGIN_* env vars. When an endpoint is configured there it is an explicit choice, so it
+ * wins over any stored credentials; Takara env is dropped because the modes are exclusive.
+ */
+function applyPluginSageMakerConfig(): boolean {
+  const arn = pluginConfigValue("MIRU_PLUGIN_SAGEMAKER_ENDPOINT_ARN");
+  if (!arn) {
+    return false;
+  }
+  process.env.MIRU_SAGEMAKER_ENDPOINT_ARN = arn;
+  const profile = pluginConfigValue("MIRU_PLUGIN_AWS_PROFILE");
+  if (profile) {
+    process.env.AWS_PROFILE = profile;
+  }
+  clearTakaraEnv();
+  activeStoredToken = null;
+  return true;
+}
+
 function hydrateSageMakerEnv(sagemaker: StoredSageMakerCredentials): void {
   process.env.MIRU_SAGEMAKER_ENDPOINT_ARN = sagemaker.endpoint_arn;
   if (sagemaker.profile && !process.env.AWS_PROFILE) {
@@ -144,6 +170,9 @@ function markLoadedToken(token: string): void {
 /** Hydrate TAKARA_API_KEY / SageMaker env vars from the credentials file when env is unset. */
 export async function loadStoredCredentials(): Promise<boolean> {
   normalizeTakaraApiKeyEnv();
+  if (applyPluginSageMakerConfig()) {
+    return true;
+  }
   const stored = await readStoredCredentials();
   if (!stored) {
     return false;