AtlasClaw Enterprise multi-user AI agent framework
EN 中文
GitHub
Embedded Mode

Transform your existing systems with an embedded AI Agent.

Without rebuilding your existing systems, embed AtlasClaw as an enterprise AI assistant to add context-aware help, cross-system intelligence, and governed Agent actions.

See the architecture Explore access modes Read integration guide
Available in v0.9.14
cloud.console / resources / vm-51478 ENTERPRISE SYSTEM
Current resource MyBG192.168.24.1612e4e resource.iaas.machine.instance.vsphere
MyBG192.168.24.1612e4e ×
Open Analyze Operations
Understanding the current page…
PAGE_CHANGED /resources/vm-51478 Live match
Fusion core

AtlasClaw understands and acts within your existing system.

Configured through embed_integration, the HostApp Provider maps pages to business objects, Domain Skills, and state-aware actions. AtlasClaw can then respond to the current Context and act through existing APIs, identity, permissions, workflows, and audit—without adding a new service or rebuilding the backend.

AtlasClaw Embedded Mode architecture for an existing enterprise system
The enterprise system adds access surfaces and a lightweight page bridge. Its existing APIs, identity, permissions, workflows, and audit remain in place.
Runs with AtlasClaw Provider package, not a new enterprise-system service
Understands your system Routes, objects, Domain Skills, and object actions
Reuses what exists Current APIs, Cookie identity, RBAC, workflows, and audit
Two access modes

One AtlasClaw Agent, available through two access points.

Independent menu access and the floating interface are two ways to reach the same AtlasClaw Agent. An enterprise system can use either one or both without duplicating the AtlasClaw integration.

01
Full-page access to the same AtlasClaw Agent

Independent menu access

Add an independent menu entry that opens AtlasClaw as a full conversational workspace. It is another access point to the same AtlasClaw Agent, not a separate AtlasClaw implementation.

  • Full chat and workspace experience
  • No page Context bridge required
  • Ideal for cross-system work
02
Help that follows the current page

Floating Assistant

Open a compact assistant above the current system page. A small message bridge publishes normalized page changes so AtlasClaw can refresh Context without exposing internal session or business payloads.

  • Compact launcher and overlay lifecycle
  • Dynamic page Context and object actions
  • Ideal for in-place analysis and operations
SmartCMP reference

AtlasClaw understands the current page, its business object, and available actions.

SmartCMP keeps its existing architecture. Its AtlasClaw Provider matches each route, resolves the visible object through existing APIs, and reuses Domain Skill action builders for both floating Context and normal Chat.

AtlasClaw floating assistant with dynamic object actions on a SmartCMP VM detail page
01 / RESOURCE CONTEXT

A VM detail route resolves to virtual_machine and smartcmp:resource. The resource Domain Skill exposes Open, Analyze, and Operations without requiring SmartCMP to send a resource DTO.

AtlasClaw offering analysis, mute, and resolve actions in an alert Context
02 / ALERT CONTEXT

An alert detail route resolves to alarm_alert and smartcmp:alarm. The alarm Domain Skill offers Analyze plus status-valid Mute, Resolve, or Reopen actions.

Virtual machine /main/virtual-machines/{resource_id}/details
OBJECT
virtual_machine
SKILL
smartcmp:resource

Open · Analyze · Operations

Alarm alert /main/alarm-activity-management/alarm-triggered/edit/{alert_id}
OBJECT
alarm_alert
SKILL
smartcmp:alarm

Analyze · Mute · Resolve · Reopen

Approval request /main/new-application/pendingApproval/{approval_type}/{approval_id}
OBJECT
approval_request
SKILL
smartcmp:approval

Analyze · Approve · Reject

Dynamic Context

From a page change to a governed action.

The enterprise system publishes navigation state. AtlasClaw and its configured HostApp Provider own the meaning, data resolution, and execution path.

  1. 01 Enterprise System

    Publish the page

    Send the normalized router path with a monotonically increasing generation.

  2. 02 Core

    Use the fixed Provider

    Select the embed_integration HostApp Provider, match one Context route, and reject stale generations.

  3. 03 HostApp Provider

    Resolve meaning and actions

    Read the object through existing system APIs and reuse its Domain Skill action builder.

  4. 04 AtlasClaw Agent

    Reason and execute

    Continue through ordinary Chat, Skill, Tool, RBAC, confirmation, and audit boundaries.

Enterprise system integration

Add a light integration without rebuilding your enterprise system.

Your enterprise system only adds access points and page lifecycle events. AtlasClaw and its configured Provider supply the intelligence while the existing architecture remains in place.

COMMON

For both surfaces

  • Embed AtlasClaw in the enterprise system's signed-in browser session.
  • Share the enterprise system Cookie so Provider calls use the same user identity and upstream permissions.
  • Keep AtlasClaw session keys, Provider configuration, and business DTOs out of cross-window messages.
MENU ACCESS

Independent menu access

  • Add an independent AtlasClaw entry in the enterprise system navigation.
  • Load the full AtlasClaw interface through that menu route.
  • No page event protocol is required.
FLOATING

Floating additionally

  • Manage launcher, iframe, ready, and close lifecycle.
  • Provide exact host origin and a per-frame nonce.
  • Send validated page changes with strict message type, nonce, and generation.
Identity and continuity

AtlasClaw acts as the same signed-in user.

Embedded authentication is Cookie-based, so Provider access shares the enterprise system's browser session and remains subject to the signed-in user's real permissions. Menu and floating surfaces can also share the active AtlasClaw Chat session; the embedding page never receives the internal session key.

Enterprise system Cookie identityProvider-side user permissionsShared active Chat sessionNo session key in embedding messages
Clear ownership

The enterprise system reports the route. AtlasClaw supplies the business meaning.

Enterprise system code does not select a Provider, send business DTOs, or decide which Skills and operations apply. AtlasClaw matches Context through the configured HostApp Provider; Domain Skills define actions, and the ordinary permission and confirmation pipeline governs execution.

Embedded AI assistant

What teams ask before bringing AtlasClaw into an existing system.

AtlasClaw adds a context-aware enterprise AI assistant while preserving the system architecture, identity, and controls already in place.

01

What is an embedded AI assistant?

An embedded AI assistant is available inside the enterprise application people already use. AtlasClaw provides independent menu access and a floating assistant so users can ask questions, understand the current page, and take governed actions without switching to a separate AI product.

02

Can AtlasClaw add an AI assistant without rebuilding the application?

Yes. The existing system keeps its backend, APIs, workflows, and audit model. A light integration adds the AtlasClaw access surfaces and, for the floating assistant, publishes normalized page changes for dynamic Context matching.

03

How does the context-aware AI assistant understand the current page?

The enterprise system publishes a normalized route change. The configured Provider matches that route to a business object, retrieves current data through existing APIs, and exposes the relevant Domain Skill and object actions to AtlasClaw.

04

Does the embedded AI Agent reuse existing user permissions?

Yes. Cookie-based authentication shares the signed-in browser session, so Provider calls remain subject to the user's existing permissions, workflows, confirmations, and audit controls. Internal AtlasClaw session keys are not exposed to the embedding page.

Start integrating

Bring AtlasClaw into your enterprise application

Start with the Embedded integration contract, then add Provider Context routes for the pages where users need analysis and action.

Explore Providers
Read Embedded integration