[codex] Move plugin implementations out of repo

[activadee]

What changed

• Removed the in-repo Automations and Voice Input plugin packages from the workspace.
• Removed the root plugins:install-dev symlink helper and the installer script.
• Updated the plugin architecture docs to describe external sibling plugin checkouts under ~/dev/<plugin_name> and manual/plugin-local installation.
• Moved the Voice Input feature spec out of docs/; it now lives with the local ~/dev/voice-input plugin checkout.

Why

The T3 Code repository should keep the plugin host, setup contracts, and shared SDK only. Plugin implementations can evolve outside this monorepo without being part of the core workspace or lockfile.

Validation

• pnpm exec vp check
• pnpm exec vp run typecheck

Note

Add plugin host infrastructure with server lifecycle, RPC endpoints, and UI rendering

• Introduces a new @t3tools/plugin-api package with contracts for server plugins, UI components, manifest schemas, and a test harness.
• Adds server-side plugin services: PluginRegistry, PluginStore, PluginHost, PluginPackageResolver, and PluginRuntimeAdapter to manage plugin lifecycle, typed key-value storage, and command invocation.
• Adds WebSocket RPC methods plugins.list, plugins.invoke, and plugins.subscribe with authorization scopes, and a new HTTP route GET /plugins/assets/* serving plugin client bundles.
• Adds database migration feat: Slash commands? #32 (plugin_documents table) to persist typed plugin collection data.
• Dynamically loads plugin client bundles in the browser via PluginHostBootstrap, registers UI factories via window.T3PluginHost, and renders plugin views at /plugins/$pluginId and /settings/plugins/$pluginId routes.
• Extends the composer to support plugin-driven send blocking, programmatic text insertion via insertComposerTextWithBoundaries, and plugin keybinding dispatch in ChatView.
• Adds plugin placements to the primary sidebar, sidebar footer, settings sidebar, and command palette based on active plugin manifests.
• Risk: Plugins load external scripts dynamically into the page; failed or slow loads degrade to placeholder UI but introduce new runtime surface area.

📊 Macroscope summarized bf1993c. 40 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted

🗂️ Filtered Issues

No issues evaluated.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: b8f7b2d5-1f5b-4a18-a925-f0e409704e3c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[macroscopeapp]

🟡 Medium plugins/PluginHost.ts:167

At line 169, if Scope.close(pluginScope, Exit.void) fails, the original commitActive error is lost. The catch handler uses Effect.andThen to chain Effect.fail(error), but if the scope close fails, andThen never executes and the scope-close error propagates instead. This is inconsistent with other Scope.close calls in this function (lines 113, 147, 157, 174) which use Effect.ignoreCause({ log: true }) to ensure cleanup errors don't mask the original failure. Consider using ignoreCause here as well, or at least ensuring the original error is preserved.

-          const displacedPluginIds = yield* activationRegistration.commitActive.pipe(
-            Effect.catch((error) =>
-              Scope.close(pluginScope, Exit.void).pipe(Effect.andThen(Effect.fail(error))),
-            ),
-          );

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/server/src/plugins/PluginHost.ts around lines 167-171:

At line 169, if `Scope.close(pluginScope, Exit.void)` fails, the original `commitActive` error is lost. The catch handler uses `Effect.andThen` to chain `Effect.fail(error)`, but if the scope close fails, `andThen` never executes and the scope-close error propagates instead. This is inconsistent with other `Scope.close` calls in this function (lines 113, 147, 157, 174) which use `Effect.ignoreCause({ log: true })` to ensure cleanup errors don't mask the original failure. Consider using `ignoreCause` here as well, or at least ensuring the original error is preserved.

Evidence trail:
apps/server/src/plugins/PluginHost.ts lines 167-171 (REVIEWED_COMMIT): `Effect.catch((error) => Scope.close(pluginScope, Exit.void).pipe(Effect.andThen(Effect.fail(error))))` — if Scope.close fails, andThen doesn't execute and original error is lost.
apps/server/src/plugins/PluginHost.ts line 113 (REVIEWED_COMMIT): `Scope.close(previousScope, Exit.void).pipe(Effect.ignoreCause({ log: true }))` — uses ignoreCause.
apps/server/src/plugins/PluginHost.ts line 147 (REVIEWED_COMMIT): `Scope.close(pluginScope, Exit.void).pipe(Effect.ignoreCause({ log: true }))` — uses ignoreCause.
apps/server/src/plugins/PluginHost.ts line 157 (REVIEWED_COMMIT): `Scope.close(previousScope, Exit.void).pipe(Effect.ignoreCause({ log: true }))` — uses ignoreCause.
apps/server/src/plugins/PluginHost.ts line 174 (REVIEWED_COMMIT): `Scope.close(previousScope, Exit.void).pipe(Effect.ignoreCause({ log: true }))` — uses ignoreCause.

[macroscopeapp]

🟡 Medium plugins/PluginStore.ts:188

In encodeDocument, line 189 calls Schema.decodeUnknownEffect(schema)(document) where document is already of type A (the decoded type). However, decodeUnknownEffect expects input matching the schema's Encoded type I. For schemas with transformations (e.g., NumberFromString where Type=number, Encoded=string), this causes decoding to fail because the function receives number when it expects string. Remove the intermediate decode step and encode directly.

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/server/src/plugins/PluginStore.ts around line 188:

In `encodeDocument`, line 189 calls `Schema.decodeUnknownEffect(schema)(document)` where `document` is already of type `A` (the decoded type). However, `decodeUnknownEffect` expects input matching the schema's `Encoded` type `I`. For schemas with transformations (e.g., `NumberFromString` where `Type=number`, `Encoded=string`), this causes decoding to fail because the function receives `number` when it expects `string`. Remove the intermediate decode step and encode directly.

Evidence trail:
- apps/server/src/plugins/PluginStore.ts lines 52, 182-208 (at REVIEWED_COMMIT): `CollectionSchema<A, I> = Schema.Codec<A, I>`; `encodeDocument` takes `document: A` and calls `Schema.decodeUnknownEffect(schema)(document)` on line 189
- pnpm-workspace.yaml line 18: effect version is 4.0.0-beta.73
- Effect Schema documentation (https://effect.website/docs/schema/introduction/): Diagram shows `decodeUnknown` goes from right-side `unknown` (expected `I` format) to `A`; `validate` goes from left-side `unknown` (expected `A` format) to `A`
- Web task confirmation: `decodeUnknown` expects Encoded (`I`) format input; calling with Type (`A`) when `A ≠ I` causes ParseError