mcpField
I
integrate-atlas-chat

integrate-atlas-chat

github.com/cognitedataAgent workflows61.9k installsUpdated 1d ago
Repository

About integrate-atlas-chat

An exception-path skill for integrating Atlas Agent chat into an app's own interface when the host Atlas sidebar cannot be used and the user has approved this approach. It directs implementers to check host compatibility first and preserve the existing product UI.

Key features

  1. 01Requires explicit approval for embedded chat
  2. 02Checks whether the host sidebar works
  3. 03Uses the Atlas chat integration guide
  4. 04Keeps the existing product interface

Use cases

  1. 01Adding embedded Atlas chat to a standalone app
  2. 02Choosing between the host sidebar and in-app chat

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/cognitedata/builder-skills --skill integrate-atlas-chat

After installing, type/integrate-atlas-chatin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

code/
client.ts
index.ts
pyodide-react.ts
pyodide-runtime.ts
pyodide.ts
python.ts
react.ts
session.test.ts
session.ts
types.ts
validation.test.ts
validation.ts

Details

From the project README

Integrate Atlas Agent Chat (exception path)

Stop. Use integrate-fusion-agent (Atlas / EOS sidebar) unless all of:

  1. The user asked for an in-app / embedded chat — not "add Atlas" / "add a chat"
  2. The host Atlas sidebar cannot work. There is no manifest field for this. Probe the app:
    • @cognite/app-sdk + connectToHostApp / useHostApp resolving inside Fusion/EOS → sidebar works; do not continue
    • Standalone-only (host connect always rejects; app is never loaded in Fusion) → in-app chat is allowed
    • If unsure, ask. Default to the sidebar.
  3. The user accepted this as the non-standard path

Then follow https://docs.cognite.com/cdf/flows/guides/ai_agent_integration and wire useAtlasChat for $ARGUMENTS. Keep the product UI; do not replace the app with a chat view.

Do not map send() / chat completions over DMS rows. If per-item completions are required: 5 per user action, ceiling 50, cache by space:externalId:lastUpdatedTime. See integrate-fusion-agent.

Comments

Markdown supported