NPM extensions for Bayon AI systems

Shared packages keep Bayon AI websites, chat surfaces, and internal tools aligned around one design language and one typed agent contract instead of copying product infrastructure across apps.

View packages Read chat docs

Extensions

These packages are the reusable Bayon AI layer: visual primitives for product websites and typed chat contracts for assistant experiences.

Published

v0.2.1

@bayonai/mui-design

Shared Bayon AI Material UI theme, tokens, page recipes, and reusable React surfaces.

Use this package when a Bayon AI React website needs the same dark visual system, panel language, Emotion cache helper, and client-side theme provider.

Bayon MUI theme, palette, typography, shadows, and component overrides
Server-safe page shells, panels, project cards, pillar cards, method boxes, and tech chips
Client-only provider, icon tooltip button, and animated Bayon flow visual

Internal

v0.1.0

@bayonai/website-agent

Shared public and internal Bayon AI agent contracts for website chat and operator workflows.

Use this package when a Bayon AI chat surface needs one source of truth for agent identity, model policy, tools, suggested prompts, and visibility boundaries.

Public Bayon Guide profile for future website chat experiences
Internal CEO/operator agent contract for company memory and planning workflows
Typed model policy, tool, prompt, visibility, and owned-document contracts

Chat package documentation

The chat package is the typed source of truth for Bayon AI assistant identity. It gives chat UIs and server routes stable agent metadata while leaving model execution, storage, and rendering in the consuming app.

Package

@bayonai/website-agent

Current version: v0.1.0

Source: packages/website-agent

Boundaries

Does not send model requests.
Does not store chat history.
Does not own UI rendering.
Does not expose internal CEO documents to public visitors.

Install

npm install @bayonai/website-agent

Inside this monorepo, consume it as a workspace package and build it with the root package scripts.

npm run build -w @bayonai/website-agent

Usage

import { getWebsiteAgent } from '@bayonai/website-agent';

const agent = getWebsiteAgent();

export function getChatConfig() {
  return {
    name: agent.name,
    model: agent.modelPolicy.preferred,
    systemPurpose: agent.summary,
    suggestedPrompts: agent.suggestedPrompts,
    tools: agent.tools,
  };
}

Integration checklist

Import `getWebsiteAgent` in the website, API route, or server action that prepares chat configuration.
Use the exported fields to seed the chat title, starter prompts, model policy, and declared tools.
Keep chat runtime behavior in the consuming app; this package owns identity and contract data only.
Never surface `bayonCeoAgent` or `getCeoAgent` in public website chat. That agent is internal-only.
Rebuild the package after contract changes so `dist/` and type declarations stay aligned.

Public chat contract

Chat UIs should depend on the exported public contract instead of duplicating prompt starters, model policy, or tool labels in component code.

`id`, `name`, `title`, `summary`, and `mission` for stable chat identity

`modelPolicy` for preferred model, fallback model, and user-selection policy

`tools` for declared capability surfaces the chat UI can expose

`suggestedPrompts` for starter actions in the chat opening state

`contactHref` for escalation into a human conversation

Building a Bayon AI app surface?

Start with the shared design extension for visual consistency, then pull agent identity from the chat package when the surface needs an assistant.

Talk to Bayon AI