​

AI Automations

SageScreen operates a fleet of autonomous AI agents that power the CI/CD pipeline, development tooling, and business automation layer. The diagram below shows the full fleet topology as of v4.

​

Fleet Diagram

If the diagram is not visible, you can open it directly at the Spaces CDN URL.

​

Architecture Overview

The SageScreen agent fleet is a set of Claude-powered coding and operations agents running inside a mono-repo CI/CD loop. Each agent is scoped to a single concern — code review, testing, deploy validation, Linear ticket automation, outreach, or document generation — and communicates through structured MCP tool calls rather than free-form messages.

​

CI/CD Agents

​

Automation Agents

​

MCP Tool Layer

All agents share a common MCP server at mcp.sagescreen.net which exposes tools for:

• Linear (issues, labels, comments)
• Pipedrive (contacts, deals, activities)
• Reply.io (sequences, enrollment)
• DigitalOcean Spaces (artifact storage and CDN)
• Productlane (changelogs, customer feedback threads)
• WordPress (posts, pages, media)

​

Transparency and Auditability

Every agent action produces a structured audit entry in the Linear issue timeline or a GitHub commit signed by the bot identity. No agent merges to dev or main without a human approval step. Secrets are never passed through agent prompts; they are resolved at runtime from environment variables injected by the CI runner.

​

Source Attribution

Fleet diagram designed by the SageScreen engineering team. SVG hosted on DigitalOcean Spaces under the sagescreen-artifacts bucket (region: nyc3).