AMaster Digital Embed SDK

Embeddable AMaster Digital React surface for Pi Agent and other host shells.

import {
  AmasterEmbedProvider,
  TaskPanelPage,
} from "@amaster.ai/amaster-digital-embed-sdk";
import "@amaster.ai/amaster-digital-embed-sdk/style.css";

export function AmasterPanel() {
  return (
    <AmasterEmbedProvider
      apiBaseUrl="http://127.0.0.1:18146/v1/amaster-digital"
      cookieAuth
      realtime={false}
    >
      <TaskPanelPage includeModalRegistry={false} />
    </AmasterEmbedProvider>
  );
}

The SDK bundles the AMaster Digital UI/core implementation. React and ReactDOM are peer dependencies.

For Pi Agent desktop, route AMaster API calls through the Pi Agent BFF. For remote runtimes, read /api/config.task_execution.remote_backend_url and point multica config set server_url at the backend that owns daemon task claims.

Publish

Run from /Users/johnsig/github/amaster-digital-multica:

npm login --auth-type=web --registry=https://registry.npmjs.org/ --userconfig=/private/tmp/amaster-digital-publish.npmrc
pnpm --filter @amaster.ai/amaster-digital-embed-sdk test
pnpm --filter @amaster.ai/amaster-digital-embed-sdk typecheck
pnpm --filter @amaster.ai/amaster-digital-embed-sdk build
npm publish --userconfig=/private/tmp/amaster-digital-publish.npmrc --ignore-scripts --access public --registry=https://registry.npmjs.org/
npm view @amaster.ai/amaster-digital-embed-sdk version --registry=https://registry.npmjs.org/

If a non-interactive publish returns EOTP, do not ask the operator for a 6-digit OTP. Re-run the same publish command in a TTY with the temporary userconfig so npm can print the publish authorization URL:

npm publish --userconfig=/private/tmp/amaster-digital-publish.npmrc --ignore-scripts --access public --registry=https://registry.npmjs.org/

Open the https://www.npmjs.com/auth/cli/... URL, let the operator approve it in the browser, then press Enter in the CLI and verify with npm view. If npm does not offer a web authorization URL, have the npm account owner publish from their own browser-authorized CLI or adjust npm publish 2FA/token policy; do not loop on OTP-only commands.

Before publishing, keep the local Pi Agent smoke path on the packed tarball:

pnpm --filter @amaster.ai/amaster-digital-embed-sdk pack --pack-destination /private/tmp
cd /Users/johnsig/github/pi-agent
pnpm --filter @amaster.ai/pi-agent-web-ui add /private/tmp/amaster.ai-amaster-digital-embed-sdk-<version>.tgz

After npm view confirms the published version, replace the Pi Agent tarball dependency with the registry version.