Angular SDK — Release Notes

@revrag-ai/embed-angular · release history, newest first. Install the latest with npm install @revrag-ai/embed-angular@latest; confirm the current version on npm.

2.0.0

Released: 26 October 2026

The first Angular release since 1.0.7. It brings the Angular package onto the current SDK engine: the agent can now see and act on your pages, and the widget reads your dashboard's widget configuration the same way the React, React Native and Android SDKs do. It also cuts the initial bundle, fixes a change-detection cost, and fixes the type files.

Every app must make one code change: pass your app's version to initialize(). Apps that call embedEvent.reset() or embedEvent.getSessionId() must also remove those calls. Every symbol you imported and every tag you placed in a template in 1.0.7 still exists: the ones that were never meant to be public are deprecated, not removed. Code that reached into the internals of those deprecated classes (for example ExpandedViewComponent.elapsedTime) may need changes.

npm install @revrag-ai/embed-angular@2.0.0

Breaking changes

Behaviour changes to check

Fields your widget configuration leaves out now use the Android SDK's defaults:

Fields your widget configuration sets now take effect:

If a colour on your dashboard was wrong but had no visible effect in 1.0.7, it will show now.

Other changes:

Deprecated

Still exported and still working; they will be removed in a later major version. They were never intended as public API.

New

• Action Intelligence — during a call the agent reads the current screen and acts on it (tap, type, select, scroll, read).
  • Starts once initialize() succeeds. Your Revrag dashboard configuration can switch it off.
  • Fields marked with data-revrag-mask (exported as MASK_ATTR), or inside an element marked with it, never have their content sent.
  • <revrag-embed-provider> highlights each element the agent acts on.
  • New provider inputs: excludeScreens, showOnAllScreens, actionRoot and getScreenName. Moving onto a screen in excludeScreens hides the widget and ends an active call. See the advanced provider guide.
  • If you narrow actionRoot, dialogs attached to document.body (such as Angular CDK dialogs) stay visible to the agent.
  • ActionIntelligenceService sets the same scope from code (type ActionScopeInputs).
• EmbedCallService — startCall(), endCall(), isCallActive().
• EmbedLogout() — call it when your user signs out. It ends any call (including one still connecting), stops the agent, wipes that user's cached screens and forgets their app_user_id (with any click events still queued for it). Your API key, widget configuration and session initialization data stay, so the next user needs no new initialize().
• Widget controls — expandWidget, collapseWidget, isWidgetExpanded, subscribeWidgetExpanded.
• Agent events — AgentEvent, embedOnAgent, embedOffAgent (types AgentEventPayload, AgentEventHandler).
• @revrag-ai/embed-angular/diagnostics — verifyIntegration() checks a setup in ten steps; integrationSnapshot() returns the current state.
• Widget
  • A draggable button that works with touch and snaps to the nearest edge.
  • Live captions (CC) during a call.
  • A ring pulses around the collapsed button during a call, in colorPalette.pulseColor or, when that is not set, your widget's main colour.
  • The fold-back after a call connects follows the dashboard's collapsedView.collapsedTime. <revrag-embed-provider> has no input for it (the bare button's autoCollapseMs input is only for provider-less setups).
  • The button size follows agentAvatar.avatarSize from your dashboard (56px when not set).
• More widget configuration fields, all set on the dashboard:
  • colorPalette.gradientColors — a gradient with any number of colours.
  • colorPalette.gradientPreset — a named gradient (ocean, sunset, aurora, midnight, …).
  • position.leftPadding and position.topPadding, and the bottom-center and top-center positions.
  • collapsedView.viewCloseDelay — how long the agent's output panel stays after its text finishes.
• Bad colours are ignored. A colour the browser cannot draw falls back to its default. Negative paddings count as 0.
• revrag-integrate.md ships in the package (node_modules/@revrag-ai/embed-angular/revrag-integrate.md) — instructions an AI coding agent can follow end to end.

Fixed

• Bundle size
  • The default avatar animation (about 400 KB) loads on demand instead of shipping in your initial bundle.
• Performance
  • The avatar animation runs outside Angular's zone. It used to trigger change detection across the whole app on every animation frame.
• Host app safety
  • The SDK loads when browser storage is blocked ("Block all cookies", sandboxed iframes).
  • Ending a call no longer removes your page's own <audio> elements.
  • Pressing call before the SDK is initialized logs a console warning instead of showing a browser alert() to your users.
• Calls
  • Mute state no longer carries over into the next call.
• Widget display
  • When the route comes from the Angular Router, screen lists (includeScreens, embedButtonVisibilityConfig) match the path only, so a ?query or #fragment in the URL no longer stops the button from showing.
• Analytics
  • Standalone apps now always report the Angular platform; it could be lost when EmbedModule was not imported.
• TypeScript
  • No type file imports the unpublished @revrag-ai/embed-core any more, so projects without skipLibCheck no longer get TS2307. See TypeScript.
• Content Security Policy
  • The in-call icons are bundled with the SDK; no image host needs to be allowed for them.
  • An avatar animation that cannot be loaded shows the SDK's own animation. The SDK no longer retries through the third-party corsproxy.io, so you can remove corsproxy.io from your CSP.

Upgrade steps: 1.0.7 → 2.0.0

1. Confirm you are on Angular 16 or newer, and check your stack against the Dependency & Compatibility Guide.
2. Install @revrag-ai/embed-angular@2.0.0. A package.json range of ^1.0.7 will not pick it up on its own.
3. Pass appVersion to initialize(), matching a version your Revrag dashboard has a widget configuration for, and catch its promise:

   this.embedInit
     .initialize('YOUR_API_KEY', { appVersion: '1.2.3' })
     .catch((err) => console.error('[Revrag] init failed:', err));

4. Remove any call to embedEvent.reset() or embedEvent.getSessionId().
5. Check your widget configuration against Behaviour changes. Set any field whose 1.0.7 behaviour you want to keep — at least the nudge fields, if you rely on the nudge.
6. If you compare event types against 'screen_view', compare against EventKeys.SCREEN_VIEW instead.
7. Mask sensitive fields with data-revrag-mask, and set excludeScreens on <revrag-embed-provider> where needed.
8. Call EmbedLogout() when your user signs out.
9. Plan to move off deprecated imports. They still work; use EmbedProviderComponent, EmbedInitService and EmbedCallService instead.
10. Optional: run verifyIntegration() from @revrag-ai/embed-angular/diagnostics to check the setup, and remove corsproxy.io from your Content Security Policy.

The Angular integration guide covers each step in detail.

1.0.7 and earlier