feat: reexport shadcn components and theme by MarioCadenas · Pull Request #2 · databricks/appkit

MarioCadenas · 2025-12-05T10:30:29Z

This PR reexports all shadcn components prepared to be easily themed + with dark/light mode out of the box.

To change the colors we only need to modify the variables in the index.css file

This shows the playground using the components plus the base theme

Dark mode

Light mode

chore: fixup

pkosiec

LGTM 👍

pkosiec · 2025-12-09T10:01:40Z

BTW it would be great to have some kind of storybook for the components 🤔 I'm actually surprised the shadcn doesn't provide this out of the box but maybe we can reuse some 3rd party registry (like https://github.com/lloydrichards/shadcn-storybook-registry - but probably this is not for us as it's v3). What do you think?

MarioCadenas · 2025-12-09T10:03:32Z

BTW it would be great to have some kind of storybook for the components 🤔 I'm actually surprised the shadcn doesn't provide this out of the box. What do you think?

well they don't have a storybook but the shadcn page itself is basically like one

https://ui.shadcn.com/docs/components

I don't know if we need that for us, what do you see it would be useful for?

pkosiec · 2025-12-09T10:05:33Z

As long as the components are 1:1 the same we don't need it badly, but once we do some patches/changes, I believe it would be great to have it up to date for users (humans) for documentation purposes 👍

Also, even if we don't patch them, having a single place with App Kit documentation would be beneficial. But it is rather nice to have, external links are fine for now 👍

## Changes  Remove all shadcn components and consume them from `@databricks/appkit-ui/react` This [PR](databricks/appkit#2) would need to be merged first. ## Why  We reexport all the components from the library and provide a base theming, allowing users to easily customize the theme by simply changing the colors in the `index.css` file ## Tests   Co-authored-by: MarioCadenas <MarioCadenas@users.noreply.github.com>

#2 — replace Object.defineProperty(signal, "aborted", ...) with vi.spyOn(signal, "aborted", "get").mockReturnValue(true). The native AbortSignal.aborted is a non-configurable getter; the previous form worked under vitest's Node env but could throw "Cannot redefine property" on stricter engines. The getter spy is vitest's idiomatic way to mock non-configurable accessors and works regardless of configurability. #3 — defensive client-side size cap on arrow_inline attachments (8 MiB), mirroring the connector cap. Prevents a misconfigured proxy or future server bug from pushing the browser into allocating an unbounded Uint8Array. Both caps carry a comment pointing to PR #320 which removes the arrow_inline SSE path entirely; that PR can drop the client cap and raise the connector cap to the API's 25 MiB hard limit when it lands. Tests: 1 new — hook rejects oversized arrow_inline payloads before decodeBase64 or processArrowBuffer is called. Co-authored-by: Isaac Signed-off-by: James Broadhead <jamesbroadhead@gmail.com>

## Changes  Remove all shadcn components and consume them from `@databricks/appkit-ui/react` This [PR](databricks/appkit#2) would need to be merged first. ## Why  We reexport all the components from the library and provide a base theming, allowing users to easily customize the theme by simply changing the colors in the `index.css` file ## Tests   Co-authored-by: MarioCadenas <MarioCadenas@users.noreply.github.com>

@example

Verified and fixed the findings from an independent code review: - #1 (correctness) expectStream dropped the wire `event:` name when the JSON payload carried its own `type` (spread ran after the assignment). Spread the payload first, then set `type = name ?? parsed.type`, so a frame like `event: error` + `data: {"type":"result"}` reports `error`. Regression test added. - #2 (contract) `@databricks/appkit/testing` eagerly loads vitest via fixtures even for `expectStream`, so vitest is a real requirement. Drop the "optional" peerDependenciesMeta and correct the docs sentence. - #6 (OBO fidelity) the fake `asUser` recorded `asUser: true` unconditionally. Enforce the real `Plugin.asUser` token precondition: a request without `x-forwarded-access-token` throws `missingToken` (missing user id throws too), and the resolved `userId` is recorded on each tool call. Tests now assert both directions (well-formed request vs token-less). - #3 (fidelity) attach() now mirrors AppKit core: registerPlugin plus registerToolProvider for real tool providers, without clobbering injected fakes. getPlugins()/getPluginNames()/hasPlugin() behave as in production. - #12 unknown-tool lookup used `tools[name] === undefined`, so a tool named "constructor"/"toString" hit Object.prototype. Use Object.hasOwn. - #5 drop data-less named SSE frames (real clients ignore them). - #7 re-export the PluginContext type from the testing barrel so MockPluginContext.ctx is nameable through the exports map. - #13 correct the docs: mock.telemetry captures the context's executeTool spans, not plugin-level spans (attachContext rebuilds the plugin's own telemetry). - #4 parseSSEResponse now delegates to the same parseSSEBody as expectStream — one parser, no divergence. All 3 analytics.integration call sites still pass. - #8 reformat template/server/example.test.ts with the template's Prettier so a scaffolded app's `npm run format` passes. - #10 fix the package-doc @example (agentsPlugin._handleStream does not exist). - #11 add kit tests that exercise attach() end-to-end (cache seed, isReady, registration, fake-not-clobbered). Build passes attw + publint; full appkit suite 3125 passed / 1 pre-existing skip. Signed-off-by: Galymzhan <zhangazy2004@gmail.com>

- #1 (P1) The docs called vitest a peer dependency, but the manifest ships it under `dependencies` (the decision we landed on, matching how appkit ships `vite` for ./type-generator). Correct the docs to match: appkit installs vitest for you, and it loads only when you import ./testing. Manifest and docs now agree. - #2 (P2) expectStream buffered the source eagerly with no bound, so a non-terminating stream hung until the runner's own timeout. Add an optional `{ timeout }` that fails fast with a clear, kit-specific error; document it and cover both directions with tests. - #3 (P2) The fake asUser replicates asUser's token precondition but not the real dev-mode `DEV_OBO_FALLBACK_KEY` OTel marker (a module-private telemetry detail). Narrow the docs and JSDoc to say so and point users at the recorded asUser/userId fields instead of isDevOboFallback(). Build passes attw + publint; full appkit suite 3141 passed / 1 pre-existing skip. Signed-off-by: Galymzhan <zhangazy2004@gmail.com>

@example

* feat(appkit): make PluginContext telemetry injectable The testing kit needs to construct a real PluginContext without a live OpenTelemetry pipeline. Add an optional constructor dependency for the telemetry provider, defaulting to the shared "plugin-context" provider so the production path is unchanged. This is the single production edit required to wrap the real class in tests rather than reimplementing it. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * feat(appkit): ship @databricks/appkit/testing and migrate first stub Wire the testing kit as a published subpath and prove it against the first of the two hand-rolled context stubs (the design gate): - Add ./testing to both exports maps (dev + publishConfig) following the ./type-generator shape, add src/testing/index.ts to the tsdown entry, and declare vitest as an optional peerDependency. Build passes attw + publint; dist/testing/{index,mock-plugin-context,expect-stream,fixtures}.{js,d.ts} are emitted and vitest stays external to the main entry. - Migrate dispatch-tool-call.test.ts: replace (plugin as any).context = { executeTool } with mockPluginContext. executeTool is now the REAL method, so the forwarded toolCallTimeoutMs is asserted through actual signal composition, the on-behalf-of (asUser) path is verified, and a new test proves the forwarded timeout actually aborts a slow toolkit tool end-to-end. This is the primary win from the plan: executeTool's OBO and timeout paths gain real assertions instead of a stub that proved nothing. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * test(appkit): migrate route-handler-errors context stub to mockPluginContext Replace the second and final hand-rolled stub — (plugin as any).context = { addRoute } — with the real PluginContext from mockPluginContext. The kit's route recorder captures raw handlers, so the alias assertion (both /invocations and /responses mount the same handler reference) holds against the real class, where forwardAsyncErrors wrapping would otherwise break reference identity. Both context stubs the plan identified are now migrated. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * docs(appkit): document the testing kit and ship a template example test - Add docs/docs/development/testing.md covering mockPluginContext(), expectStream(), and the fixture helpers, with a full end-to-end example. Cross-links to local-development, custom-plugins, and execution-context. - Add template/server/example.test.ts: a self-contained, plugin-agnostic example that scaffolded apps ship with — it defines a tiny custom plugin and exercises both mockPluginContext (route recording) and expectStream (ordered event assertions), running with no workspace or network. Ships the kit to users, satisfying the plan's acceptance criteria that a docs page exists and the template carries at least one example test. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * docs(appkit): fix testing-kit examples to instantiate the plugin class Validation by scaffolding a real app with `databricks apps init` surfaced that the examples called the `analytics()`/`toPlugin()` factory and then treated the result as a plugin instance — but a factory returns a { plugin, config, name } descriptor for createApp to construct, so `.attachContext`/handler methods are absent. Rewrite both the template example test and the docs "Full example" to instantiate the plugin class directly (`new GreeterPlugin({})`), matching how the migrated agents suites use the kit. The scaffolded app's `npm test` and `tsc` both pass against the published `@databricks/appkit/testing` subpath with no workspace or network. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * refactor(appkit): tighten FakeToolResponse so a missing value is a type error Drop `undefined` from the static FakeToolValue union. `resolve()` treats an undefined map entry as "unregistered tool" and throws, so allowing undefined as a declared response made `{ query: undefined }` a confusing runtime error instead of a compile error. A function returning undefined still works for the rare "returns nothing" case. Add a test pinning that a null response is returned as a value, not misread as a missing tool. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * refactor(appkit): make tools/test-helpers a shim over the shipped testing kit The plan's step 5 was to MOVE the fixtures into the package, not copy them. The shipped kit (src/testing/fixtures.ts) duplicated all 15 exports of tools/test-helpers.ts, which would drift over time. Collapse the original into a thin re-export of @databricks/appkit/testing so src/testing is the single source of truth while the 18 existing @tools/test-helpers importers keep working unchanged. The re-exported mockServiceContext is now synchronous; every call site either awaits it (no-op on a non-promise) or reads it through Awaited<ReturnType<...>>, so all suites pass unchanged (full appkit suite: 3117 passed, 1 pre-existing skip). Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * fix(appkit): normalize CRLF in expectStream SSE parsing; sharpen testing docs Code review follow-ups: - expectStream's parseSSEBody split frames on \n\n, so a spec-compliant SSE stream delimited by \r\n\r\n (from a real server) collapsed into one event. AppKit's own writer uses \n\n so existing tests were unaffected, but expectStream is public API that accepts any Response. Normalize CRLF to LF before splitting; add a CRLF regression test. - Docs: instantiate the plugin CLASS in the attach() snippet (the factory returns a descriptor, not an instance), and note that the cache attach() seeds is a per-process singleton shared by tests within a file. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * fix(appkit): resolve repo-wide Biome error blocking CI CI's "Lint & Type Check" job runs `pnpm run check` over the whole repo, so a pre-existing lint error unrelated to this branch failed the build: - remote-tunnel-controller.test.ts had two `afterEach` hooks in one describe (lint/suspicious/noDuplicateTestHooks, error severity). Merge them into one — behavior preserved (env reset + console-spy clear both still run after each test). This file is byte-identical to main; the error predated the branch and only surfaced because CI lints the entire tree. Also drop two dead `biome-ignore lint/suspicious/noExplicitAny` suppressions in the testing kit (fixtures.ts, expect-stream.test.ts): `noExplicitAny` is turned off repo-wide in biome.json, so the comments had no effect (suppressions/unused warnings). The invalid-source test now casts through `unknown as never`. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * fix(appkit): address cross-model review findings in the testing kit Verified and fixed the findings from an independent code review: - #1 (correctness) expectStream dropped the wire `event:` name when the JSON payload carried its own `type` (spread ran after the assignment). Spread the payload first, then set `type = name ?? parsed.type`, so a frame like `event: error` + `data: {"type":"result"}` reports `error`. Regression test added. - #2 (contract) `@databricks/appkit/testing` eagerly loads vitest via fixtures even for `expectStream`, so vitest is a real requirement. Drop the "optional" peerDependenciesMeta and correct the docs sentence. - #6 (OBO fidelity) the fake `asUser` recorded `asUser: true` unconditionally. Enforce the real `Plugin.asUser` token precondition: a request without `x-forwarded-access-token` throws `missingToken` (missing user id throws too), and the resolved `userId` is recorded on each tool call. Tests now assert both directions (well-formed request vs token-less). - #3 (fidelity) attach() now mirrors AppKit core: registerPlugin plus registerToolProvider for real tool providers, without clobbering injected fakes. getPlugins()/getPluginNames()/hasPlugin() behave as in production. - #12 unknown-tool lookup used `tools[name] === undefined`, so a tool named "constructor"/"toString" hit Object.prototype. Use Object.hasOwn. - #5 drop data-less named SSE frames (real clients ignore them). - #7 re-export the PluginContext type from the testing barrel so MockPluginContext.ctx is nameable through the exports map. - #13 correct the docs: mock.telemetry captures the context's executeTool spans, not plugin-level spans (attachContext rebuilds the plugin's own telemetry). - #4 parseSSEResponse now delegates to the same parseSSEBody as expectStream — one parser, no divergence. All 3 analytics.integration call sites still pass. - #8 reformat template/server/example.test.ts with the template's Prettier so a scaffolded app's `npm run format` passes. - #10 fix the package-doc @example (agentsPlugin._handleStream does not exist). - #11 add kit tests that exercise attach() end-to-end (cache seed, isReady, registration, fake-not-clobbered). Build passes attw + publint; full appkit suite 3125 passed / 1 pre-existing skip. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * chore(appkit): drop knip vitest-ignore now that vitest is a real peer dep With vitest declared as a (non-optional) peerDependency, knip recognizes it as used, so the earlier ignoreDependencies entry is unnecessary. This reverts knip.json to its original state. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * fix(appkit): make vitest a normal dependency, not a package-wide peer A required peerDependency has no per-subpath scope: it applied to the whole @databricks/appkit package, so every production consumer that never imports the testing kit got an unsatisfied peer (npm 7+ auto-installs vitest into their tree; pnpm warns) — a wider blast radius than the eager-import bug it was meant to fix. Follow appkit's own precedent instead: `vite` backs the ./type-generator subpath as a normal `dependency`, installed for everyone but loaded only by importers of that subpath. Do the same for `vitest` and ./testing. vitest is referenced solely by dist/testing/fixtures.js, never by the main/plugin/core entry, so a consumer importing createApp never loads it. Verified end-to-end: scaffolded an app whose own vitest (4.1.9) differs in major from appkit's dependency (3.2.4), forcing a nested second copy. The testing kit's vi.fn()/vi.spyOn() mocks and expect(...).toHaveBeenCalled() assertions work across the two instances (vi spies carry their own call state), and npm install emits no peer-dep warning. Build passes attw + publint. Also fold in the template example's Prettier formatting (template uses Prettier, not Biome) so a scaffolded app's `npm run format` passes. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * refactor(appkit): rename mockPluginContext to createTestPluginContext The helper builds the REAL PluginContext with faked edges — it does not mock the context — so the name was misleading. Rename to createTestPluginContext (and the MockPluginContext type to TestPluginContext), matching the create*-for-tests convention, and rename the files to test-plugin-context.ts. Pre-merge and unreleased, so no external consumers are affected. Also finish the #13 doc-accuracy fix in the shipped JSDoc (not just the docs page): the telemetry field comment now states it captures the context's spans (executeTool), not plugin-internal spans — attachContext rebuilds the plugin's this.telemetry from the real TelemetryManager. These comments ship in dist/testing/*.d.ts, so IntelliSense previously showed the unqualified claim. Build passes attw + publint; full appkit suite 3125 passed / 1 pre-existing skip. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * refactor(appkit): dedupe testing fixtures and tidy test-plugin-context Behavior-preserving cleanups in the testing kit: - createMockRequest reuses createMockWorkspaceClient() instead of an inline copy of the same mock client (verified identical). - createMockServiceContext / createMockUserContext / mockServiceContext inline the createMockWorkspaceClient() call into the `||` fallback, so the mock client is built only when the caller did not supply one. - The fake asUser view spreads `...base` and overrides executeAgentTool rather than re-declaring getAgentTools. - expectStream's isSubsequence breaks once the expected sequence is fully matched. No semantic change; typecheck clean and all kit + migrated tests pass. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * fix(appkit): resolve third-review findings in the testing kit - #1 (P1) The docs called vitest a peer dependency, but the manifest ships it under `dependencies` (the decision we landed on, matching how appkit ships `vite` for ./type-generator). Correct the docs to match: appkit installs vitest for you, and it loads only when you import ./testing. Manifest and docs now agree. - #2 (P2) expectStream buffered the source eagerly with no bound, so a non-terminating stream hung until the runner's own timeout. Add an optional `{ timeout }` that fails fast with a clear, kit-specific error; document it and cover both directions with tests. - #3 (P2) The fake asUser replicates asUser's token precondition but not the real dev-mode `DEV_OBO_FALLBACK_KEY` OTel marker (a module-private telemetry detail). Narrow the docs and JSDoc to say so and point users at the recorded asUser/userId fields instead of isDevOboFallback(). Build passes attw + publint; full appkit suite 3141 passed / 1 pre-existing skip. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * test(appkit): dogfood the testing kit on analytics and genie plugins Exercise @databricks/appkit/testing against real core plugins to validate it beyond the two agent proof sites and produce usage references: - analytics.kit.test.ts: cross-plugin executeTool via createTestPluginContext — OBO identity (asUser/userId), token-precondition rejection, and per-call timeout abort. Needs only the kit (no workspace/ServiceContext). - genie.kit.test.ts: drives the real _handleSendMessage SSE stream and asserts event order with expectStream(...).toEmit(...). Both add genuinely new coverage (streamed SSE order + OBO dispatch identity were untested). Full appkit suite 3145 passed / 1 pre-existing skip. Developer-experience notes (kit wins + friction, e.g. createMockResponse doesn't compose with expectStream) captured in internal/ for the milestone review. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * refactor(appkit): address testing-kit review feedback Resolve the eight review comments on the testing kit: - createMockResponse now captures written SSE bytes and exposes sseResponse(); expectStream reads a captured mock response directly, so streaming-route tests no longer need a hand-rolled bridge. - Ship vitest as an optional peer dependency (+ devDependency) instead of a plain runtime dependency, keeping the test framework out of production installs and deduping to the app's own copy. Ignore it in knip. - Add an obo option to createMockRequest so on-behalf-of tests set the forwarded identity headers with one flag. - Add resetTestCache() to clear the shared cache singleton between tests. - Use the documented attach() instead of an any-cast in the agents dispatch tests. - Drop the unused createMockServiceContext/createMockUserContext builders from the public surface; keep the service-context builder internal. - Pin the previously untested edges: the Object.hasOwn tool-lookup guard, the dev-mode asUser branch, and parseSSEBody's non-object data values. - Add useServiceContextMock() to register the mock lifecycle in one line, returning a live accessor. Dogfood the new helpers in the analytics, genie, and serving suites, and document them in the testing guide. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * docs(appkit): move the testing guide under Plugins The testing kit is entirely plugin-scoped (createTestPluginContext, attach(plugin), plugin route/tool/SSE assertions), and the page's own cross-links already pointed into plugins/. Move it next to custom-plugins and fix the relative links. Keep the heading as 'Testing'; the Plugins section supplies the context. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * test(appkit): fold dogfood tests into plugin suites Address round-2 review: the kit should be the default way to test a plugin, not a parallel '*.kit.test.ts' track. - Fold the three cross-plugin executeTool OBO tests into analytics.test.ts and delete analytics.kit.test.ts. - Upgrade genie.test.ts's SSE test to assert event ORDER via expectStream on genie's real event names (message_start, status, message_result, query_result), replacing brittle write.mock.calls substring checks, and delete genie.kit.test.ts. - Trim the heavy comment narration from the folded-in tests. - Re-export createTestPluginContext and expectStream from the test-helpers shim. - Finish the testing-guide move under plugins/ (sidebar position + links). Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * test(appkit): restore toHaveLength(1) on the analytics OBO dispatch test The dogfood fold trimmed expect(mock.toolCalls).toHaveLength(1), so a double-dispatch would no longer fail the happy-path test — and it was inconsistent with the token-less sibling that kept toHaveLength(0). Restore it. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * test(appkit): re-assert genie SSE payloads after the expectStream swap The toEmit swap pinned event order but dropped the payload values the old substring checks covered (conversationId=new-conv-id, status=ASKING_AI), which aren't asserted elsewhere. Restore them structurally via collect() + toMatchObject — keeping the ordering guarantee without brittle substrings. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * fix(appkit): drop fabricated workspace-client fields from createMockRequest createMockRequest returned userWorkspaceClient, serviceWorkspaceClient, getWarehouseId and getWorkspaceId — fields no production code reads (plugins resolve those through getWorkspaceClient()/getWarehouseId() from src/context, which mockServiceContext stands in for). Publishing them via @databricks/appkit/testing would make four inert fields a permanent public promise. The two warehouse cold-start tests (analytics + metric) overrode mockReq.serviceWorkspaceClient.warehouses.get, which the route never reads — so they passed on the default RUNNING client without exercising the warehouse path at all. Route the warehouse client through mockServiceContext (the real seam) so the tests are live, and drop the 'mock WorkspaceClient' claim from the testing guide. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * chore: drop the .claude ignores and restore the client lockfile Both were swept into the oxlint merge from a dirty working tree and corrected later on the branch; folding those corrections in here keeps them out of the follow-up PR. The knip `.claude/**` entry and the `**/.claude` ignorePatterns in oxfmt/oxlint were never needed — nothing in the repo lints or formats that directory. The `packages/appkit` vitest ignoreDependencies entry stays: vitest is a real dependency of the testing entry. apps/dev-playground/client/package-lock.json is restored to origin/main byte-for-byte; npm had run in that directory and pruned its `extraneous: true` entries. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> * fix(appkit): lowercase mock request header keys, as Express does `createMockRequest` stored header keys exactly as given while `header()` lowercased the lookup, so a mixed-case override was unreachable: createMockRequest({ obo: { userId: "alice" }, headers: { "X-Forwarded-User": "bob" } }); // header("x-forwarded-user") === "alice" Both keys were kept — ["x-forwarded-access-token", "x-forwarded-user", "X-Forwarded-User"] — and the lowercase one obo seeded still answered, which contradicted the "an explicit override wins" contract documented right above it. Keys are now lowercased on the way in, matching what Node's parser hands Express. Thanks @pkosiec. The existing override test passed because it used a lowercase key, so it is now parametrised over both casings, and the case-insensitivity test additionally pins that every stored key is lowercase. Reverting the fix fails both. Signed-off-by: Galymzhan <zhangazy2004@gmail.com> --------- Signed-off-by: Galymzhan <zhangazy2004@gmail.com>

MarioCadenas force-pushed the ui-components branch 2 times, most recently from 6ebcef4 to 7c5ae71Compare December 5, 2025 10:45

MarioCadenas mentioned this pull request Dec 5, 2025
feat: use library components databricks/cli#4099
Merged

MarioCadenas force-pushed the ui-components branch from 7c5ae71 to d053b4fCompare December 9, 2025 09:06

MarioCadenas requested review from a team, ditadi and pkosiec December 9, 2025 09:06

feat: reexport shadcn components and theme
c20a0f7
chore: fixup

MarioCadenas force-pushed the ui-components branch from d053b4f to c20a0f7Compare December 9, 2025 09:10

pkosiec approved these changes Dec 9, 2025
View reviewed changes

Comment threadbiome.json

MarioCadenas merged commit 4964c07 into mainDec 9, 2025
3 checks passed

MarioCadenas deleted the ui-components branch December 19, 2025 17:43

pkosiec mentioned this pull request Apr 2, 2026
feat(files): per-volume in-app policy enforcement #197
Merged
5 tasks

pkosiec mentioned this pull request Apr 15, 2026
feat: Lakeflow Jobs Plugin #265
Merged
3 tasks

This was referenced May 4, 2026
feat(appkit): send internal telemetry via AppkitLog schema #332
Merged
feat(appkit): tools(plugins) DX, runAgent plugins arg, shared toolkit-resolver #305
Merged

MarioCadenas mentioned this pull request May 7, 2026
feat(appkit): agents() plugin, createAgent(def), and markdown-driven agents #304
Merged

pkosiec mentioned this pull request May 12, 2026
feat(appkit): reference agent-app, dev-playground chat UI, docs, and template #306
Merged

pkosiec mentioned this pull request May 20, 2026
feat: add source-map support for editor DOM mapping #347
Merged
3 tasks

pkosiec mentioned this pull request May 21, 2026
chore: add prerelease SDK packaging #397
Merged

MarioCadenas mentioned this pull request May 21, 2026
fix(appkit): decouple cache in-flight execution from per-caller abort… #398
Merged
4 tasks

MarioCadenas mentioned this pull request Jul 16, 2026
feat(appkit): managed eval datasets + turn semantics (stack 3/5) #479
Open

MarioCadenas mentioned this pull request Aug 6, 2026
fix(cli): resolve transitive registryDependencies and surface optional resource env vars #516
Closed

Navigation Menu

Uh oh!

feat: reexport shadcn components and theme - #2

feat: reexport shadcn components and theme#2
MarioCadenas merged 1 commit into
mainfrom
ui-components

MarioCadenas commented Dec 5, 2025•
edited
Loading

Uh oh!

pkosiec left a comment

Uh oh!

Uh oh!

pkosiec commented Dec 9, 2025•
edited
Loading

Uh oh!

MarioCadenas commented Dec 9, 2025

Uh oh!

pkosiec commented Dec 9, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

MarioCadenas commented Dec 5, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pkosiec left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

pkosiec commented Dec 9, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

MarioCadenas commented Dec 9, 2025

Uh oh!

pkosiec commented Dec 9, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

MarioCadenas commented Dec 5, 2025•
edited
Loading

pkosiec commented Dec 9, 2025•
edited
Loading