@agent-relay/dashboard 2.0.81 → 2.0.82

package/src/landing/SecurityPage.tsx

@@ -0,0 +1,42 @@
+/**
+ * Agent Relay Cloud - Security Page
+ */
+
+import React from 'react';
+import { StaticPage } from './StaticPage';
+
+export function SecurityPage() {
+  return (
+    <StaticPage
+      title="Security"
+      subtitle="How we protect your code and data."
+    >
+      <h2>Data Handling</h2>
+      <ul>
+        <li>Your source code is processed in isolated, ephemeral containers</li>
+        <li>Repository access tokens are scoped to minimum required permissions</li>
+        <li>All data is encrypted in transit using TLS</li>
+        <li>Credentials are encrypted at rest</li>
+      </ul>
+
+      <h2>Authentication</h2>
+      <ul>
+        <li>OAuth 2.0 authentication via GitHub</li>
+        <li>Session management with automatic timeout</li>
+      </ul>
+
+      <h2>AI Providers</h2>
+      <p>
+        We integrate with AI providers who maintain their own security standards. We recommend reviewing each provider's data handling policies.
+      </p>
+
+      <h2>Contact</h2>
+      <p>
+        For security questions or to report vulnerabilities, contact us at{' '}
+        <a href="mailto:security@agent-relay.com">security@agent-relay.com</a>.
+      </p>
+    </StaticPage>
+  );
+}
+
+export default SecurityPage;

package/src/landing/StaticPage.tsx

@@ -0,0 +1,165 @@
+/**
+ * Agent Relay Cloud - Static Page Layout
+ *
+ * Shared layout component for static content pages (About, Privacy, Terms, etc.)
+ * Provides consistent navigation, footer, and content styling.
+ */
+
+import React from 'react';
+import './styles.css';
+import { LogoIcon } from '../components/Logo';
+
+interface StaticPageProps {
+  title: string;
+  titleLink?: string;
+  subtitle?: string;
+  children: React.ReactNode;
+  lastUpdated?: string;
+}
+
+export function StaticPage({ title, titleLink, subtitle, children, lastUpdated }: StaticPageProps) {
+  return (
+    <div className="landing-page static-page">
+      <div className="landing-bg">
+        <GridBackground />
+        <GlowOrbs />
+      </div>
+
+      <StaticNavigation />
+
+      <main>
+        <section className="static-hero">
+          <div className="static-hero-content">
+            <h1>{titleLink ? <a href={titleLink} style={{ color: 'inherit', textDecoration: 'none' }}>{title}</a> : title}</h1>
+            {subtitle && <p className="static-subtitle">{subtitle}</p>}
+            {lastUpdated && <p className="static-updated">Last updated: {lastUpdated}</p>}
+          </div>
+        </section>
+
+        <section className="static-content">
+          <div className="content-container">
+            {children}
+          </div>
+        </section>
+      </main>
+
+      <StaticFooter />
+    </div>
+  );
+}
+
+function StaticNavigation() {
+  return (
+    <nav className="nav scrolled">
+      <div className="nav-inner">
+        <a href="/" className="nav-logo">
+          <LogoIcon size={28} withGlow={true} />
+          <span className="logo-text">Agent Relay</span>
+        </a>
+
+        <div className="nav-links">
+          <a href="/#demo">Demo</a>
+          <a href="/#features">Features</a>
+          <a href="/pricing">Pricing</a>
+          <a href="https://docs.agent-relay.com/" className="nav-docs">Docs</a>
+        </div>
+
+        <div className="nav-actions">
+          <a href="/login" className="btn-ghost">Sign In</a>
+          <a href="/signup" className="btn-primary">Get Started</a>
+        </div>
+      </div>
+    </nav>
+  );
+}
+
+function StaticFooter() {
+  return (
+    <footer className="footer">
+      <div className="footer-inner">
+        <div className="footer-brand">
+          <a href="/" className="footer-logo">
+            <LogoIcon size={24} withGlow={true} />
+            <span className="logo-text">Agent Relay</span>
+          </a>
+          <p>Orchestrate AI agents like a symphony.</p>
+        </div>
+
+        <div className="footer-links">
+          <div className="footer-column">
+            <h4>Product</h4>
+            <a href="/#features">Features</a>
+            <a href="/pricing">Pricing</a>
+            <a href="https://docs.agent-relay.com/">Documentation</a>
+            <a href="/changelog">Changelog</a>
+          </div>
+          <div className="footer-column">
+            <h4>Company</h4>
+            <a href="/about">About</a>
+            <a href="/blog">Blog</a>
+            <a href="/careers">Careers</a>
+            <a href="/contact">Contact</a>
+          </div>
+          <div className="footer-column">
+            <h4>Legal</h4>
+            <a href="/privacy">Privacy</a>
+            <a href="/terms">Terms</a>
+            <a href="/security">Security</a>
+          </div>
+        </div>
+      </div>
+
+      <div className="footer-bottom">
+        <p>&copy; 2026 Agent Relay. All rights reserved.</p>
+        <div className="social-links">
+          <a href="https://github.com/AgentWorkforce/relay" aria-label="GitHub">
+            <GitHubIcon />
+          </a>
+          <a href="https://twitter.com/agent_relay" aria-label="Twitter">
+            <TwitterIcon />
+          </a>
+                  </div>
+      </div>
+    </footer>
+  );
+}
+
+// Background components
+function GridBackground() {
+  return (
+    <div className="grid-bg">
+      <div className="grid-lines" />
+      <div className="grid-glow" />
+    </div>
+  );
+}
+
+function GlowOrbs() {
+  return (
+    <div className="glow-orbs">
+      <div className="orb orb-1" />
+      <div className="orb orb-2" />
+      <div className="orb orb-3" />
+    </div>
+  );
+}
+
+// Icons
+function GitHubIcon() {
+  return (
+    <svg width="20" height="20" viewBox="0 0 24 24" fill="currentColor">
+      <path d="M12 0C5.37 0 0 5.37 0 12c0 5.31 3.435 9.795 8.205 11.385.6.105.825-.255.825-.57 0-.285-.015-1.23-.015-2.235-3.015.555-3.795-.735-4.035-1.41-.135-.345-.72-1.41-1.23-1.695-.42-.225-1.02-.78-.015-.795.945-.015 1.62.87 1.845 1.23 1.08 1.815 2.805 1.305 3.495.99.105-.78.42-1.305.765-1.605-2.67-.3-5.46-1.335-5.46-5.925 0-1.305.465-2.385 1.23-3.225-.12-.3-.54-1.53.12-3.18 0 0 1.005-.315 3.3 1.23.96-.27 1.98-.405 3-.405s2.04.135 3 .405c2.295-1.56 3.3-1.23 3.3-1.23.66 1.65.24 2.88.12 3.18.765.84 1.23 1.905 1.23 3.225 0 4.605-2.805 5.625-5.475 5.925.435.375.81 1.095.81 2.22 0 1.605-.015 2.895-.015 3.3 0 .315.225.69.825.57A12.02 12.02 0 0024 12c0-6.63-5.37-12-12-12z" />
+    </svg>
+  );
+}
+
+function TwitterIcon() {
+  return (
+    <svg width="20" height="20" viewBox="0 0 24 24" fill="currentColor">
+      <path d="M18.244 2.25h3.308l-7.227 8.26 8.502 11.24H16.17l-5.214-6.817L4.99 21.75H1.68l7.73-8.835L1.254 2.25H8.08l4.713 6.231zm-1.161 17.52h1.833L7.084 4.126H5.117z" />
+    </svg>
+  );
+}
+
+
+export default StaticPage;

package/src/landing/TermsPage.tsx

@@ -0,0 +1,125 @@
+/**
+ * Agent Relay Cloud - Terms of Service Page
+ */
+
+import React from 'react';
+import { StaticPage } from './StaticPage';
+
+export function TermsPage() {
+  return (
+    <StaticPage
+      title="Terms of Service"
+      subtitle="The rules of the road for using Agent Relay."
+      lastUpdated="January 15, 2026"
+    >
+      <h2>Agreement to Terms</h2>
+      <p>
+        By accessing or using Agent Relay ("Service"), you agree to be bound by these Terms of Service ("Terms"). If you do not agree, please do not use our Service.
+      </p>
+
+      <h2>Description of Service</h2>
+      <p>
+        Agent Relay is an AI agent orchestration platform that enables developers to deploy, coordinate, and monitor multiple AI agents working together on software development tasks. Our Service includes web-based dashboards, APIs, and integrations with AI providers and code repositories.
+      </p>
+
+      <h2>Account Registration</h2>
+      <p>To use certain features of the Service, you must register for an account. You agree to:</p>
+      <ul>
+        <li>Provide accurate, current, and complete information</li>
+        <li>Maintain and update your information as needed</li>
+        <li>Keep your password secure and confidential</li>
+        <li>Accept responsibility for all activities under your account</li>
+        <li>Notify us immediately of any unauthorized use</li>
+      </ul>
+
+      <h2>Acceptable Use</h2>
+      <p>You agree not to use the Service to:</p>
+      <ul>
+        <li>Violate any applicable laws or regulations</li>
+        <li>Generate malicious code, malware, or security exploits</li>
+        <li>Harass, abuse, or harm others</li>
+        <li>Infringe on intellectual property rights</li>
+        <li>Attempt to gain unauthorized access to our systems</li>
+        <li>Interfere with or disrupt the Service</li>
+        <li>Reverse engineer or decompile the Service</li>
+        <li>Use automated means to access the Service without permission</li>
+        <li>Circumvent usage limits or billing controls</li>
+      </ul>
+
+      <h2>AI Provider Terms</h2>
+      <p>
+        Our Service integrates with third-party AI providers (Anthropic, OpenAI, Google). By using these integrations, you also agree to comply with their respective terms of service and usage policies. You are responsible for ensuring your use complies with all applicable AI provider terms.
+      </p>
+
+      <h2>Intellectual Property</h2>
+      <h3>Your Content</h3>
+      <p>
+        You retain ownership of all code, data, and content you provide to the Service ("Your Content"). By using the Service, you grant us a limited license to process Your Content solely to provide the Service.
+      </p>
+
+      <h3>Our Property</h3>
+      <p>
+        The Service, including its design, features, and documentation, is owned by Agent Relay and protected by intellectual property laws. You may not copy, modify, or distribute our intellectual property without permission.
+      </p>
+
+      <h2>Payment Terms</h2>
+      <p>
+        Paid plans are billed in advance on a monthly or annual basis. All fees are non-refundable except as required by law or as explicitly stated otherwise. We may change pricing with 30 days' notice.
+      </p>
+      <ul>
+        <li>Free tier usage is subject to specified limits</li>
+        <li>Exceeding plan limits may result in service throttling or additional charges</li>
+        <li>Failed payments may result in service suspension</li>
+      </ul>
+
+      <h2>Service Availability</h2>
+      <p>
+        We strive to maintain 99.9% uptime but do not guarantee uninterrupted access. We may perform maintenance or updates that temporarily affect availability. We are not liable for any damages resulting from service interruptions.
+      </p>
+
+      <h2>Limitation of Liability</h2>
+      <p>
+        TO THE MAXIMUM EXTENT PERMITTED BY LAW, AGENT RELAY SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS OR REVENUES, WHETHER INCURRED DIRECTLY OR INDIRECTLY, OR ANY LOSS OF DATA, USE, GOODWILL, OR OTHER INTANGIBLE LOSSES.
+      </p>
+      <p>
+        OUR TOTAL LIABILITY FOR ANY CLAIMS ARISING FROM THESE TERMS OR THE SERVICE SHALL NOT EXCEED THE AMOUNT YOU PAID US IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM.
+      </p>
+
+      <h2>Disclaimer of Warranties</h2>
+      <p>
+        THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. WE DISCLAIM ALL WARRANTIES INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.
+      </p>
+      <p>
+        AI-generated outputs may contain errors. You are responsible for reviewing and validating all code and content produced by agents before use in production.
+      </p>
+
+      <h2>Indemnification</h2>
+      <p>
+        You agree to indemnify and hold harmless Agent Relay from any claims, damages, or expenses arising from your use of the Service, your violation of these Terms, or your violation of any rights of a third party.
+      </p>
+
+      <h2>Termination</h2>
+      <p>
+        You may terminate your account at any time through your account settings. We may suspend or terminate your access for violation of these Terms or for any other reason with notice. Upon termination, your right to use the Service ceases immediately.
+      </p>
+
+      <h2>Governing Law</h2>
+      <p>
+        These Terms are governed by the laws of the State of Delaware, without regard to conflict of law principles. Any disputes shall be resolved in the courts of Delaware.
+      </p>
+
+      <h2>Changes to Terms</h2>
+      <p>
+        We may modify these Terms at any time. Material changes will be notified via email or through the Service. Continued use after changes constitutes acceptance of the new Terms.
+      </p>
+
+      <h2>Contact</h2>
+      <p>
+        Questions about these Terms? Contact us at{' '}
+        <a href="mailto:legal@agent-relay.com">legal@agent-relay.com</a>.
+      </p>
+    </StaticPage>
+  );
+}
+
+export default TermsPage;

package/src/landing/blogData.ts

@@ -0,0 +1,312 @@
+/**
+ * Agent Relay Cloud - Blog Post Data
+ */
+
+export interface BlogPost {
+  id: string;
+  title: string;
+  subtitle: string;
+  date: string;
+  author: string;
+  category: string;
+  excerpt: string;
+  content: string;
+}
+
+export const blogPosts: BlogPost[] = [
+  {
+    id: 'let-them-cook-multi-agent-orchestration',
+    title: 'Let Them Cook: Lessons from 6 Weeks of Multi-Agent Orchestration',
+    subtitle: 'What I learned watching AI agents coordinate, communicate, and occasionally fall apart',
+    date: 'February 4, 2026',
+    author: 'Khaliq Gant',
+    category: 'Engineering',
+    excerpt: 'Multi-agent orchestration is a step change in how tasks get done. After 6 weeks of building with agent swarms, here\'s what works, what breaks, and why the planning phase becomes everything.',
+    content: `
+I've been building [Agent Relay](https://github.com/AgentWorkforce/relay) using Agent Relay. Agents coordinating to build the tool that lets them coordinate. It sounds recursive because it is. I took some time to jot down some thoughts about multi-agent orchestration from the past few weeks where I've spoken to agents more than I've spoken to my wife 😳.
+
+For the past six weeks, I've been deep in this world. Agent Relay is an open-source communication layer allowing any CLI tool (Claude, Cursor, OpenCode, Gemini) to communicate efficiently and seamlessly. And it's rumored that Claude Code is coming out with first-party support for agent swarms:
+
+{{tweet:https://twitter.com/nummanali/status/2014698883507462387}}
+
+Am I worried about this? If I'm being completely honest, yes, a little bit. But my main feeling is that it's great to push multi-agent orchestration into the forefront of developer minds so the true power can be experienced and more best practices form around it.
+
+## Key Takeaways
+
+- **2-5 worker agents per Lead** is the sweet spot
+- **Claude for coordination, Codex for deep work** (match the CLI to the role)
+- **Planning is everything** (agents cut corners on vague specs)
+- **Shadow agents and reviewers** catch lazy work
+- **Store trajectories** so future agents have context
+
+
+## Part 1: The Promise
+
+Multi-agent orchestration is a step change in how tasks get done. It puts agents front and center while the human takes a step back and just lets them cook. That doesn't mean the human will be completely removed. There are still bumps in the road to truly autonomous agent work, and the planning phase becomes one of the most crucial steps.
+
+### What Multi-Agent Unlocks
+
+Having agents who can communicate with each other and coordinate on tasks is a huge unlock. Assigning [agent profiles](https://github.com/AgentWorkforce/relay/tree/main/.claude/agents) similar to how human teams would organize has been a paradigm I have found success with. For instance:
+
+- **Lead** – coordinates the team and breaks down tasks
+- **Backend** – implements server-side logic
+- **BackendReviewer** – reviews backend code for quality
+- **FrontendReviewer** – reviews frontend code for quality
+- **TypeChecker** – ensures type safety across the codebase
+- **TestWriter** – writes and maintains tests
+- **DocumentationExpert** – handles docs and comments
+
+Each agent assumes its role, can read the logs of other agents, and can message others to check their work, sanity-check their decisions, and hand off tasks in a coordinated manner.
+
+### The Speed Improvement
+
+The method that has worked well for me is creating a detailed spec upfront and then spawning a Lead agent. I give it the spec and tell it to assemble a team as it sees fit. The Lead then spawns agents accordingly. Because Agent Relay is CLI-agnostic, I make sure to mix Codex, Claude, OpenCode, Gemini, and Droid agents, assigning different models based on the role. A fast model like Haiku or Conductor for Lead roles, and for deeper technical tasks, Opus or GPT-5 Codex high.
+
+Using this workflow, I've seen that not only does code quality increase, but the speed at which agents can pump out complex features is at least a **4-5X improvement**.
+
+I have been using Agent Relay to build itself on the cloud environment at [agent-relay.com](https://agent-relay.com) and the pace of delivery has been mind-blowing.
+
+It hasn't been all good though...
+
+
+## Part 2: The Problems
+
+### Agents Are Sometimes Lazy
+
+I've had instances where an agent swarm takes on a complicated feature and then the Lead excitedly declares everything done. On one build, the Lead proudly reported "All 12 endpoints implemented!" When I tested it, only 8 actually returned data. The rest were stubbed out with TODOs. This happened occasionally with single-agent sessions, but imagine it compounding across 5, 6, or 10 agents...
+
+### Agents Get Overwhelmed and Die
+
+Having a Lead agent creates a single point of failure. If the swarm is large and chatty, the Lead receives a flood of messages from other agents plus queries from the human asking about status or redirecting work. This can overwhelm the Lead, causing it to enter an endless loop and eventually die or become completely unresponsive.
+
+
+## Part 3: The Playbook
+
+Here's what I've learned about making multi-agent orchestration actually work.
+
+### Team Structure
+
+Team structure is critical. There's a magic ratio of Lead-to-worker agents that I haven't exactly figured out yet (it varies depending on roles) but I've had success with **2-5 worker agents per Lead**. A single Lead managing 10 agents usually becomes problematic.
+
+### Communication Patterns by CLI
+
+Not all CLI agents communicate the same way, and taking this into account is beneficial when working with swarms.
+
+**Codex** is great at heads-down work but doesn't communicate well. Once it's working, it's hard to interrupt. I've had Leads waiting 15+ minutes for a response, assuming the agent died, when Codex was just deep in implementation.
+
+**Claude** communicates excellently and can be interrupted mid-task without issue. It naturally provides status updates and asks clarifying questions.
+
+**Cursor** (particularly Composer) is very fast and communicates well, making it good for rapid iteration.
+
+**My staffing rule of thumb:** Put Claude agents in Lead and Reviewer roles where communication is key. Put Codex agents on isolated implementation tasks where heads-down focus is more valuable than status updates. Use Cursor when you need speed and tight feedback loops.
+
+Agent Relay allows users to define a \`teams.json\` ([docs](https://docs.agent-relay.com/reference/configuration#project-configuration-files)) that auto-spawns agents on start, so these staffing decisions can be codified and stay consistent across sessions:
+
+\`\`\`json
+{
+  "team": "my-team",
+  "autoSpawn": true,
+  "agents": [
+    {
+      "name": "Coordinator",
+      "cli": "claude",
+      "role": "coordinator",
+      "task": "Coordinate the team..."
+    },
+    {
+      "name": "Developer",
+      "cli": "codex",
+      "task": "Implement features..."
+    }
+  ]
+}
+\`\`\`
+
+### Catching Lazy Work
+
+Agent Relay has a notion of a [**shadow agent**](https://docs.agent-relay.com/features/shadows#shadow-agents) that helps quite a bit with this problem. Reviewer agents also typically catch shoddy work.
+
+![Agent Relay dashboard showing Developer reporting completion to Coordinator, who then routes the work to ReviewerA for review](/blog/agent-review-workflow.png)
+
+Additionally, layering in one of the many AI code review tools has been effective at catching minor issues.
+
+### Continuity and Hooks
+
+Agent Relay has a [\`continuity\`](https://docs.agent-relay.com/guides/session-continuity#session-continuity) concept, largely borrowed from the [Continuous Claude](https://github.com/parcadei/Continuous-Claude-v3) package by [@parcadei](https://x.com/parcadei). This enables ephemeral agents that save their context periodically, get released, then spawn again and continue seamlessly by reading their saved state.
+
+If you want more granular control or access to agent lifecycle events, Agent Relay has an extensive [hooks system](https://docs.agent-relay.com/guides/hooks) with 7 different events:
+
+| Hook | Description |
+|------|-------------|
+| \`onSessionStart\` | Agent starts |
+| \`onSessionEnd\` | Agent stops |
+| \`onOutput\` | Agent produces output |
+| \`onMessageReceived\` | Receives relay message |
+| \`onMessageSent\` | Sends relay message |
+| \`onIdle\` | Agent inactive |
+| \`onError\` | Error occurs |
+
+### Trajectories: Preserving Context
+
+One unexpected unlock has been having agents store **trajectories**, a train of thought stored in logical chapters for a completed task. Inspired by [this thread](https://x.com/gergelyorosz/status/2002160432841097239) from [@GergelyOrosz](https://x.com/GergelyOrosz).
+
+\`\`\`json
+{
+  "id": "traj_itn5hyej5mi6",
+  "task": { "title": "Fix module resolution issues" },
+  "status": "completed",
+  "chapters": [
+    {
+      "title": "Work",
+      "events": [
+        {
+          "type": "decision",
+          "content": "Thread shadowMode through protocol layers",
+          "raw": { "reasoning": "Devin review found fields were silently dropped..." },
+          "significance": "high"
+        }
+      ]
+    }
+  ],
+  "retrospective": {
+    "summary": "Fixed issue by threading shadow options through all layers",
+    "confidence": 0.9
+  }
+}
+\`\`\`
+
+The [AgentWorkforce/trajectories](https://github.com/AgentWorkforce/trajectories/) repo provides a CLI tool that agents can easily understand. It becomes invaluable when an agent needs to revisit a previously-worked feature or investigate a bug. By finding the relevant trajectory, the agent gains instant context. These trajectories are also useful to humans reviewing the codebase.
+
+### The Human's New Role
+
+Coordinating with multiple agents and seeing output fly in at rapid speed is exhilarating. Being able to remove myself as the bottleneck is a huge benefit. This necessitates that the **planning phase is carefully and meticulously done** to ensure agents have well-defined tasks with edge cases thought out.
+
+It also means the **review phase is paramount**. Having agents self-review and cross-review is an effective strategy.
+
+
+## Try It Yourself
+
+Want to experiment with multi-agent orchestration? You can [get started with Agent Relay Cloud](https://agent-relay.com) or set it up locally in seconds.
+
+Just tell your CLI agent to run:
+
+\`\`\`bash
+curl -s https://raw.githubusercontent.com/AgentWorkforce/relay/main/docs/guide/agent-setup.md
+\`\`\`
+
+The agent will read the setup guide and configure everything, then let it cook.
+
+Check out the [docs](https://docs.agent-relay.com) for more details, or hit me on X with any thoughts or questions. I'm all for a discussion: [@khaliqgant](https://x.com/khaliqgant)
+
+## References
+
+- [Cursor: Scaling Agents](https://cursor.com/blog/scaling-agents) – An interesting perspective on how Cursor is thinking about agent scaling and the challenges involved
+- [@pbteja1998 on multi-agent swarms with OpenClaw](https://x.com/pbteja1998/status/2017662163540971756) – Exciting developments in how people are experimenting with multi-agent orchestration
+`,
+  },
+  {
+    id: 'go-to-bed-wake-up-to-a-finished-product',
+    title: 'Go to Bed, Wake Up to a Finished Product',
+    subtitle: 'How agent-to-agent communication is changing autonomous development',
+    date: 'February 1, 2026',
+    author: 'Khaliq Gant',
+    category: 'Vision',
+    excerpt: 'Agent-to-agent communication is weird, fascinating, and potentially revolutionary. Here\'s how we built a system where agents work autonomously while we sleep.',
+    content: `
+The clear and obvious takeaway from [OpenClaw](https://openclaw.ai/) (Moltbot) and [Moltbook](https://www.moltbook.com/) is that agent-to-agent communication is first of all weird and fascinating, but the potential this unlocks is also unprecedented and potentially revolutionary.
+
+On December 16th, we started a project where we wanted to get two Claude agents to play tic-tac-toe against each other. We first dug into Agent Mail and [made a proof of concept](https://github.com/Dicklesworthstone/mcp_agent_mail/pull/33) there, but quickly realized the limitations of a pull-based methodology. We kept digging and quickly realized the only way to get an agent to autonomously interact with other agents is a push-based method that delivers messages directly to their input. So was born [Agent Relay](https://github.com/AgentWorkforce/relay).
+
+## Ok...I'm intrigued, go on...
+
+Agent-to-agent communication across any CLI tool (Codex, Claude, Gemini, OpenCode, Droid, etc.) is possible **right now** for any task. This can be done via an easy-to-use SDK or the relay-dashboard where you can see messages across agents, chat, spawn and release agents as needed.
+
+At the base level, Agent Relay is a protocol which makes it easy and reliable to stage CLI-agnostic agent-to-agent communication. The tools built on top of that protocol are the [relay-dashboard](https://github.com/AgentWorkforce/relay-dashboard/) and [relay-tui](https://github.com/AgentWorkforce/relay-tui) — but could be relay-slack, relay-discord -- you name it!
+
+As we see with Moltbook and what I've seen for the past month: **agents are creative, efficient, sometimes lazy and cut corners, chatty, and but mostly it is clear that they work quite effectively when given roles and clear responsibilities.**
+
+I kept finding myself as the clear bottleneck when working on projects, so removing myself and replacing with an agent is a huge accelerator. I found myself spending more time planning and producing detailed specs. I'd hand that to a "Lead" agent, ask them to review it, staff a team accordingly, and just let me know of any blockers.
+
+Then I would [go to bed](https://x.com/khaliqgant/status/2008325804741071079) and wake up to a finished product.
+
+## Why Not Just Sub-Agents?
+
+Using actual agent instances is a more powerful abstraction. Your agents can create sub-agents, giving the agent much more power. When giving a sub-agent a task too big or complex, it'll often hit compaction (context window limits) and just stop—which completely breaks the autonomous workflow we're looking for.
+
+## How Do I Use This?
+
+There are a few ways to use Relay:
+
+### For Developers
+
+**1.** Start a relay server and use the dashboard to spawn and chat with agents:
+
+\`\`\`bash
+npm install -g agent-relay
+agent-relay up --dashboard
+\`\`\`
+
+**2.** Start a \`claude\` | \`codex\` etc session and tell it to install and start agent-relay by following the instructions here:
+
+\`\`\`bash
+$ claude
+
+╭────────────────────────────────────────╮
+│ ✻ Welcome to Claude Code!              │
+│                                        │
+│   /help for help                       │
+│                                        │
+╰────────────────────────────────────────╯
+
+> Install and configure agent-relay by following the instructions here:
+  curl -s https://raw.githubusercontent.com/AgentWorkforce/relay/main/docs/guide/agent-setup.md
+\`\`\`
+
+The agent will read the setup guide and start a relay session, ready to coordinate with other agents.
+
+### For Library Developers
+
+Use our SDK to enable agent-to-agent communication in your app:
+
+\`\`\`bash
+# Install agent relay and start the daemon
+npm install -g agent-relay
+agent-relay up
+
+# In your project
+npm install agent-relay
+\`\`\`
+
+\`\`\`javascript
+import { RelayClient } from 'agent-relay';
+
+const client = new RelayClient({ name: 'MyApp' });
+await client.connect();
+
+// Spawn a worker agent
+await client.spawn({
+  name: 'Worker',
+  cli: 'claude',
+  task: 'Wait for instructions'
+});
+
+// Send it a message
+await client.send('Worker', 'Hello from my app');
+\`\`\`
+
+Check out our [docs](https://docs.agent-relay.com/) for more info.
+
+## What's Next
+
+We're super excited for what's to come. [Agent Relay Cloud](https://agent-relay.com/) allows you, via GitHub login, to link your repository to your own private workspace server. Using your Claude, Codex, Gemini, or Cursor login, you can spawn agents and have them work 24/7 against your repo using the dashboard.
+
+You and your teammates who have access to the repository can interact with agents, giving instructions in different topic-based channels to help organize agent work. You can have agents review pull requests, work on documentation—all with authenticated access to your GitHub repo.
+
+This is just the beginning. GitHub is the first context we've unlocked. This will be extended to other integrations like Notion, Slack, Outlook, etc., so agents can operate 24/7 and accelerate your workflows.
+    `,
+  },
+];
+
+export function getBlogPost(id: string): BlogPost | undefined {
+  return blogPosts.find(post => post.id === id);
+}

package/src/landing/index.ts

@@ -0,0 +1,18 @@
+/**
+ * Agent Relay Cloud - Landing Page Module
+ */
+
+export { LandingPage, default } from './LandingPage';
+export { PricingPage } from './PricingPage';
+export { StaticPage } from './StaticPage';
+export { PrivacyPage } from './PrivacyPage';
+export { TermsPage } from './TermsPage';
+export { SecurityPage } from './SecurityPage';
+export { AboutPage } from './AboutPage';
+export { ContactPage } from './ContactPage';
+export { DocsPage } from './DocsPage';
+export { ChangelogPage } from './ChangelogPage';
+export { BlogPage } from './BlogPage';
+export { blogPosts, getBlogPost, type BlogPost } from './blogData';
+export { renderBlogContent } from './BlogContent';
+export { CareersPage } from './CareersPage';