zilmate 1.7.8 → 1.8.1

package/.agents/skills/agentmail/references/websockets.md

@@ -0,0 +1,263 @@
+# WebSockets
+
+WebSockets provide real-time, low-latency email event streaming over a persistent connection. No public URL required.
+
+## When to Use
+
+- Local development (no ngrok needed)
+- Client-side applications
+- When you need bidirectional communication
+- Lower latency than webhooks
+
+For production with public endpoints, [webhooks.md](webhooks.md) may be simpler.
+
+## Comparison
+
+| Feature    | Webhook                | WebSocket         |
+| ---------- | ---------------------- | ----------------- |
+| Setup      | Requires public URL    | No external tools |
+| Connection | HTTP request per event | Persistent        |
+| Latency    | HTTP round-trip        | Instant streaming |
+| Firewall   | Must expose port       | Outbound only     |
+
+## TypeScript SDK
+
+### Basic Usage
+
+```typescript
+import { AgentMailClient, AgentMail } from "agentmail";
+
+const client = new AgentMailClient({ apiKey: process.env.AGENTMAIL_API_KEY });
+
+async function main() {
+  const socket = await client.websockets.connect();
+
+  socket.on("open", () => {
+    console.log("Connected");
+    socket.sendSubscribe({
+      type: "subscribe",
+      inboxIds: ["agent@agentmail.to"],
+    });
+  });
+
+  socket.on("message", (event: AgentMail.MessageReceivedEvent) => {
+    if (event.eventType === "message.received") {
+      console.log("From:", event.message.from);
+      console.log("Subject:", event.message.subject);
+    }
+  });
+
+  socket.on("close", (event) => console.log("Disconnected:", event.code));
+  socket.on("error", (error) => console.error("Error:", error));
+}
+
+main();
+```
+
+### React Hook
+
+```typescript
+import { useEffect, useState } from "react";
+import { AgentMailClient, AgentMail } from "agentmail";
+
+function useAgentMailWebSocket(apiKey: string, inboxIds: string[]) {
+  const [lastMessage, setLastMessage] =
+    useState<AgentMail.MessageReceivedEvent | null>(null);
+  const [isConnected, setIsConnected] = useState(false);
+
+  useEffect(() => {
+    const client = new AgentMailClient({ apiKey });
+    let socket: Awaited<ReturnType<typeof client.websockets.connect>>;
+
+    async function connect() {
+      socket = await client.websockets.connect();
+
+      socket.on("open", () => {
+        setIsConnected(true);
+        socket.sendSubscribe({ type: "subscribe", inboxIds });
+      });
+
+      socket.on("message", (event) => {
+        if (event.eventType === "message.received") {
+          setLastMessage(event);
+        }
+      });
+
+      socket.on("close", () => setIsConnected(false));
+    }
+
+    connect();
+    return () => socket?.close();
+  }, [apiKey, inboxIds.join(",")]);
+
+  return { lastMessage, isConnected };
+}
+```
+
+## Python SDK
+
+### Sync Usage
+
+```python
+from agentmail import AgentMail, Subscribe, Subscribed, MessageReceivedEvent
+
+client = AgentMail(api_key="YOUR_API_KEY")
+
+with client.websockets.connect() as socket:
+    # Subscribe to inboxes
+    socket.send_subscribe(Subscribe(inbox_ids=["agent@agentmail.to"]))
+
+    # Process events
+    for event in socket:
+        if isinstance(event, Subscribed):
+            print(f"Subscribed to: {event.inbox_ids}")
+        elif isinstance(event, MessageReceivedEvent):
+            print(f"From: {event.message.from_}")
+            print(f"Subject: {event.message.subject}")
+```
+
+### Async Usage
+
+```python
+import asyncio
+from agentmail import AsyncAgentMail, Subscribe, MessageReceivedEvent
+
+client = AsyncAgentMail(api_key="YOUR_API_KEY")
+
+async def main():
+    async with client.websockets.connect() as socket:
+        await socket.send_subscribe(Subscribe(inbox_ids=["agent@agentmail.to"]))
+
+        async for event in socket:
+            if isinstance(event, MessageReceivedEvent):
+                print(f"New: {event.message.subject}")
+
+asyncio.run(main())
+```
+
+### Event Handler Pattern
+
+```python
+import threading
+from agentmail import AgentMail, Subscribe, EventType
+
+client = AgentMail(api_key="YOUR_API_KEY")
+
+with client.websockets.connect() as socket:
+    socket.on(EventType.OPEN, lambda _: print("Connected"))
+    socket.on(EventType.MESSAGE, lambda msg: print("Received:", msg))
+    socket.on(EventType.CLOSE, lambda _: print("Disconnected"))
+    socket.on(EventType.ERROR, lambda err: print("Error:", err))
+
+    socket.send_subscribe(Subscribe(inbox_ids=["agent@agentmail.to"]))
+
+    # Run listener in background thread
+    listener = threading.Thread(target=socket.start_listening, daemon=True)
+    listener.start()
+    listener.join()
+```
+
+## Subscribe Options
+
+Filter events by inbox, pod, or event type.
+
+```typescript
+socket.sendSubscribe({
+  type: "subscribe",
+  inboxIds: ["agent@agentmail.to"],
+  eventTypes: ["message.received", "message.sent"],
+});
+
+// By pods
+socket.sendSubscribe({
+  type: "subscribe",
+  podIds: ["pod_123", "pod_456"],
+});
+```
+
+```python
+from agentmail import Subscribe
+
+# By inboxes
+Subscribe(inbox_ids=["inbox1@agentmail.to", "inbox2@agentmail.to"])
+
+# By pods
+Subscribe(pod_ids=["pod_123", "pod_456"])
+
+# By event types
+Subscribe(
+    inbox_ids=["agent@agentmail.to"],
+    event_types=["message.received", "message.sent"]
+)
+```
+
+## Event Types
+
+| Event                  | TypeScript Type                    | Python Class             |
+| ---------------------- | ---------------------------------- | ------------------------ |
+| Subscription confirmed | `AgentMail.Subscribed`             | `Subscribed`             |
+| New email received     | `AgentMail.MessageReceivedEvent`   | `MessageReceivedEvent`   |
+| Email sent             | `AgentMail.MessageSentEvent`       | `MessageSentEvent`       |
+| Email delivered        | `AgentMail.MessageDeliveredEvent`  | `MessageDeliveredEvent`  |
+| Email bounced          | `AgentMail.MessageBouncedEvent`    | `MessageBouncedEvent`    |
+| Spam complaint         | `AgentMail.MessageComplainedEvent` | `MessageComplainedEvent` |
+| Email rejected         | `AgentMail.MessageRejectedEvent`   | `MessageRejectedEvent`   |
+| Domain verified        | `AgentMail.DomainVerifiedEvent`    | `DomainVerifiedEvent`    |
+
+## Message Properties
+
+The `event.message` object contains (Python snake_case / TypeScript camelCase):
+
+| Python             | TypeScript      | Description                           |
+| ------------------ | --------------- | ------------------------------------- |
+| `inbox_id`         | `inboxId`       | Inbox that received the email         |
+| `message_id`       | `messageId`     | Unique message ID                     |
+| `thread_id`        | `threadId`      | Conversation thread ID                |
+| `from_`            | `from`          | Sender address (string)               |
+| `to`               | `to`            | Recipients list (list of strings)     |
+| `subject`          | `subject`       | Subject line                          |
+| `text`             | `text`          | Plain text body                       |
+| `html`             | `html`          | HTML body (if present)                |
+| `extracted_text`   | `extractedText` | Reply content, quoted history stripped |
+| `attachments`      | `attachments`   | List of attachments                   |
+| `labels`           | `labels`        | List of labels                        |
+
+Python uses `from_` because `from` is a reserved keyword; TypeScript uses `from` directly.
+
+## Error Handling
+
+```typescript
+import { AgentMailClient, AgentMailError } from "agentmail";
+
+try {
+  const socket = await client.websockets.connect();
+  // ...
+} catch (err) {
+  if (err instanceof AgentMailError) {
+    console.error(`API error: ${err.statusCode} - ${err.message}`);
+  } else {
+    console.error("Connection error:", err);
+  }
+}
+```
+
+```python
+from agentmail import AsyncAgentMail, Subscribe, MessageReceivedEvent
+from agentmail.core.api_error import ApiError
+
+client = AsyncAgentMail(api_key="YOUR_API_KEY")
+
+async def main():
+    try:
+        async with client.websockets.connect() as socket:
+            await socket.send_subscribe(Subscribe(inbox_ids=["agent@agentmail.to"]))
+
+            async for event in socket:
+                if isinstance(event, MessageReceivedEvent):
+                    await process_email(event.message)
+
+    except ApiError as e:
+        print(f"API error: {e.status_code} - {e.body}")
+    except Exception as e:
+        print(f"Connection error: {e}")
+```

package/.agents/skills/ai-elements/SKILL.md

@@ -0,0 +1,160 @@
+---
+name: ai-elements
+description: Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface.
+---
+
+# AI Elements
+
+[AI Elements](https://www.npmjs.com/package/ai-elements) is a component library and custom registry built on top of [shadcn/ui](https://ui.shadcn.com/) to help you build AI-native applications faster. It provides pre-built components like conversations, messages and more.
+
+Installing AI Elements is straightforward and can be done in a couple of ways. You can use the dedicated CLI command for the fastest setup, or integrate via the standard shadcn/ui CLI if you've already adopted shadcn's workflow.
+
+> **IMPORTANT:** Run all CLI commands using the project's package runner: `npx ai-elements@latest`, `pnpm dlx ai-elements@latest`, or `bunx --bun ai-elements@latest` — based on the project's `packageManager`. Examples below use `npx ai-elements@latest` but substitute the correct runner for the project.
+
+## Prerequisites
+
+Before installing AI Elements, make sure your environment meets the following requirements:
+
+- [Node.js](https://nodejs.org/en/download/), version 18 or later
+- A [Next.js](https://nextjs.org/) project with the [AI SDK](https://ai-sdk.dev/) installed.
+- [shadcn/ui](https://ui.shadcn.com/) installed in your project. If you don't have it installed, running any install command will automatically install it for you.
+- We also highly recommend using the [AI Gateway](https://vercel.com/docs/ai-gateway) and adding `AI_GATEWAY_API_KEY` to your `env.local` so you don't have to use an API key from every provider. AI Gateway also gives $5 in usage per month so you can experiment with models. You can obtain an API key [here](https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fai%2Fapi-keys&title=Get%20your%20AI%20Gateway%20key).
+
+## Installing Components
+
+You can install AI Elements components using either the AI Elements CLI or the shadcn/ui CLI. Both achieve the same result: adding the selected component’s code and any needed dependencies to your project.
+
+The CLI will download the component’s code and integrate it into your project’s directory (usually under your components folder). By default, AI Elements components are added to the `@/components/ai-elements/` directory (or whatever folder you’ve configured in your shadcn components settings).
+
+After running the command, you should see a confirmation in your terminal that the files were added. You can then proceed to use the component in your code.
+
+## Usage
+
+Once an AI Elements component is installed, you can import it and use it in your application like any other React component. The components are added as part of your codebase (not hidden in a library), so the usage feels very natural.
+
+## Example
+
+After installing AI Elements components, you can use them in your application like any other React component. For example:
+
+```tsx title="conversation.tsx"
+"use client";
+
+import {
+  Message,
+  MessageContent,
+  MessageResponse,
+} from "@/components/ai-elements/message";
+import { useChat } from "@ai-sdk/react";
+
+const Example = () => {
+  const { messages } = useChat();
+
+  return (
+    <>
+      {messages.map(({ role, parts }, index) => (
+        <Message from={role} key={index}>
+          <MessageContent>
+            {parts.map((part, i) => {
+              switch (part.type) {
+                case "text":
+                  return (
+                    <MessageResponse key={`${role}-${i}`}>
+                      {part.text}
+                    </MessageResponse>
+                  );
+              }
+            })}
+          </MessageContent>
+        </Message>
+      ))}
+    </>
+  );
+};
+
+export default Example;
+```
+
+In the example above, we import the `Message` component from our AI Elements directory and include it in our JSX. Then, we compose the component with the `MessageContent` and `MessageResponse` subcomponents. You can style or configure the component just as you would if you wrote it yourself – since the code lives in your project, you can even open the component file to see how it works or make custom modifications.
+
+## Extensibility
+
+All AI Elements components take as many primitive attributes as possible. For example, the `Message` component extends `HTMLAttributes<HTMLDivElement>`, so you can pass any props that a `div` supports. This makes it easy to extend the component with your own styles or functionality.
+
+## Customization
+
+After installation, no additional setup is needed. The component’s styles (Tailwind CSS classes) and scripts are already integrated. You can start interacting with the component in your app immediately.
+
+For example, if you'd like to remove the rounding on `Message`, you can go to `components/ai-elements/message.tsx` and remove `rounded-lg` as follows:
+
+```tsx title="components/ai-elements/message.tsx" highlight="8"
+export const MessageContent = ({
+  children,
+  className,
+  ...props
+}: MessageContentProps) => (
+  <div
+    className={cn(
+      "flex flex-col gap-2 text-sm text-foreground",
+      "group-[.is-user]:bg-primary group-[.is-user]:text-primary-foreground group-[.is-user]:px-4 group-[.is-user]:py-3",
+      className
+    )}
+    {...props}
+  >
+    <div className="is-user:dark">{children}</div>
+  </div>
+);
+```
+
+## Troubleshooting
+
+### Why are my components not styled?
+
+Make sure your project is configured correctly for shadcn/ui in Tailwind 4 - this means having a `globals.css` file that imports Tailwind and includes the shadcn/ui base styles.
+
+### I ran the AI Elements CLI but nothing was added to my project
+
+Double-check that:
+
+- Your current working directory is the root of your project (where `package.json` lives).
+- Your components.json file (if using shadcn-style config) is set up correctly.
+- You’re using the latest version of the AI Elements CLI:
+
+```bash title="Terminal"
+npx ai-elements@latest
+```
+
+If all else fails, feel free to open an [issue on GitHub](https://github.com/vercel/ai-elements/issues).
+
+### Theme switching doesn’t work — my app stays in light mode
+
+Ensure your app is using the same data-theme system that shadcn/ui and AI Elements expect. The default implementation toggles a data-theme attribute on the `<html>` element. Make sure your tailwind.config.js is using class or data- selectors accordingly.
+
+### The component imports fail with “module not found”
+
+Check the file exists. If it does, make sure your `tsconfig.json` has a proper paths alias for `@/` i.e.
+
+```json title="tsconfig.json"
+{
+  "compilerOptions": {
+    "baseUrl": ".",
+    "paths": {
+      "@/*": ["./*"]
+    }
+  }
+}
+```
+
+### My AI coding assistant can't access AI Elements components
+
+1. Verify your config file syntax is valid JSON.
+2. Check that the file path is correct for your AI tool.
+3. Restart your coding assistant after making changes.
+4. Ensure you have a stable internet connection.
+
+### Still stuck?
+
+If none of these answers help, open an [issue on GitHub](https://github.com/vercel/ai-elements/issues) and someone will be happy to assist.
+
+## Available Components
+
+See the `references/` folder for detailed documentation on each component.

package/.agents/skills/ai-elements/references/agent.md

@@ -0,0 +1,134 @@
+# Agent
+
+A composable component for displaying AI agent configuration with model, instructions, tools, and output schema.
+
+The `Agent` component displays an interface for showing AI agent configuration details. It's designed to represent a configured agent from the AI SDK, showing the agent's model, system instructions, available tools (with expandable input schemas), and output schema.
+
+See `scripts/agent.tsx` for this example.
+
+## Installation
+
+```bash
+npx ai-elements@latest add agent
+```
+
+## Usage with AI SDK
+
+Display an agent's configuration alongside your chat interface. Tools are displayed in an accordion where clicking the description expands to show the input schema.
+
+```tsx title="app/page.tsx"
+"use client";
+
+import { tool } from "ai";
+import { z } from "zod";
+import {
+  Agent,
+  AgentContent,
+  AgentHeader,
+  AgentInstructions,
+  AgentOutput,
+  AgentTool,
+  AgentTools,
+} from "@/components/ai-elements/agent";
+
+const webSearch = tool({
+  description: "Search the web for information",
+  inputSchema: z.object({
+    query: z.string().describe("The search query"),
+  }),
+});
+
+const readUrl = tool({
+  description: "Read and parse content from a URL",
+  inputSchema: z.object({
+    url: z.string().url().describe("The URL to read"),
+  }),
+});
+
+const outputSchema = `z.object({
+  sentiment: z.enum(['positive', 'negative', 'neutral']),
+  score: z.number(),
+  summary: z.string(),
+})`;
+
+export default function Page() {
+  return (
+    <Agent>
+      <AgentHeader
+        name="Sentiment Analyzer"
+        model="anthropic/claude-sonnet-4-5"
+      />
+      <AgentContent>
+        <AgentInstructions>
+          Analyze the sentiment of the provided text and return a structured
+          analysis with sentiment classification, confidence score, and summary.
+        </AgentInstructions>
+        <AgentTools>
+          <AgentTool tool={webSearch} value="web_search" />
+          <AgentTool tool={readUrl} value="read_url" />
+        </AgentTools>
+        <AgentOutput schema={outputSchema} />
+      </AgentContent>
+    </Agent>
+  );
+}
+```
+
+## Features
+
+- Model badge in header
+- Instructions rendered as markdown
+- Tools displayed as accordion items with expandable input schemas
+- Output schema display with syntax highlighting
+- Composable structure for flexible layouts
+- Works with AI SDK `Tool` type
+
+## Props
+
+### `<Agent />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `...props` | `React.ComponentProps<` | - | Any props are spread to the root div. |
+
+### `<AgentHeader />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `name` | `string` | Required | The name of the agent. |
+| `model` | `string` | - | The model identifier (e.g.  |
+| `...props` | `React.ComponentProps<` | - | Any other props are spread to the container div. |
+
+### `<AgentContent />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `...props` | `React.ComponentProps<` | - | Any other props are spread to the container div. |
+
+### `<AgentInstructions />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `children` | `string` | Required | The instruction text. |
+| `...props` | `React.ComponentProps<` | - | Any other props are spread to the container div. |
+
+### `<AgentTools />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `...props` | `React.ComponentProps<typeof Accordion>` | - | Any other props are spread to the Accordion component. |
+
+### `<AgentTool />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `tool` | `Tool` | Required | The tool object from the AI SDK containing description and inputSchema. |
+| `value` | `string` | Required | Unique identifier for the accordion item. |
+| `...props` | `React.ComponentProps<typeof AccordionItem>` | - | Any other props are spread to the AccordionItem component. |
+
+### `<AgentOutput />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `schema` | `string` | Required | The output schema as a string (displayed with syntax highlighting). |
+| `...props` | `React.ComponentProps<` | - | Any other props are spread to the container div. |

package/.agents/skills/ai-elements/references/artifact.md

@@ -0,0 +1,84 @@
+# Artifact
+
+A container component for displaying generated content like code, documents, or other outputs with built-in actions.
+
+The `Artifact` component provides a structured container for displaying generated content like code, documents, or other outputs with built-in header actions.
+
+See `scripts/artifact.tsx` for this example.
+
+## Installation
+
+```bash
+npx ai-elements@latest add artifact
+```
+
+## Features
+
+- Structured container with header and content areas
+- Built-in header with title and description support
+- Flexible action buttons with tooltips
+- Customizable styling for all subcomponents
+- Support for close buttons and action groups
+- Clean, modern design with border and shadow
+- Responsive layout that adapts to content
+- TypeScript support with proper type definitions
+- Composable architecture for maximum flexibility
+
+## Examples
+
+### With Code Display
+
+See `scripts/artifact.tsx` for this example.
+
+## Props
+
+### `<Artifact />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `...props` | `React.HTMLAttributes<HTMLDivElement>` | - | Any other props are spread to the underlying div element. |
+
+### `<ArtifactHeader />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `...props` | `React.HTMLAttributes<HTMLDivElement>` | - | Any other props are spread to the underlying div element. |
+
+### `<ArtifactTitle />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `...props` | `React.HTMLAttributes<HTMLParagraphElement>` | - | Any other props are spread to the underlying paragraph element. |
+
+### `<ArtifactDescription />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `...props` | `React.HTMLAttributes<HTMLParagraphElement>` | - | Any other props are spread to the underlying paragraph element. |
+
+### `<ArtifactActions />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `...props` | `React.HTMLAttributes<HTMLDivElement>` | - | Any other props are spread to the underlying div element. |
+
+### `<ArtifactAction />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `tooltip` | `string` | - | Tooltip text to display on hover. |
+| `label` | `string` | - | Screen reader label for the action button. |
+| `icon` | `LucideIcon` | - | Lucide icon component to display in the button. |
+| `...props` | `React.ComponentProps<typeof Button>` | - | Any other props are spread to the underlying shadcn/ui Button component. |
+
+### `<ArtifactClose />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `...props` | `React.ComponentProps<typeof Button>` | - | Any other props are spread to the underlying shadcn/ui Button component. |
+
+### `<ArtifactContent />`
+
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `...props` | `React.HTMLAttributes<HTMLDivElement>` | - | Any other props are spread to the underlying div element. |