From 0c4089063a39d00ab74db14c1d50dda64e77496d Mon Sep 17 00:00:00 2001 From: Kishore Kumar Date: Thu, 18 Jun 2026 18:30:03 +0530 Subject: [PATCH 1/3] docs: reposition around the fleet of AI teammates; swap stealth callout for early-access CTA MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - README + index.mdx lead with "a fleet of prebuilt AI teammates for recurring engineering work" instead of "a resident engineer for support escalations". - index.mdx: replace the "stealth-mode / private alpha" Warning with a "Get early access" CTA pointing at the Clerk waitlist (accounts.agentsfleet.net/waitlist); keep the design-partner email as the secondary path. - Rework the "2am problem" section into "a teammate that owns the outcome" — PR + deploy framing, scenario-backed fix, human approval before merge/ship. - Historical changelog entries left untouched (append-only). Co-Authored-By: Claude Opus 4.8 (1M context) --- README.md | 4 ++-- index.mdx | 16 ++++++++-------- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index e8d8225..7922863 100644 --- a/README.md +++ b/README.md @@ -6,9 +6,9 @@ agentsfleet -**A resident engineer for your support escalations.** +**A fleet of prebuilt AI teammates for recurring engineering work.** -Takes a ticket through investigation across your code, telemetry, and live control-plane state. Proposes a fix, waits for human approval, then ships it or drafts the customer reply. Runs against a durable, replayable log — posts evidenced answers, never chats. +Each one wakes on an event — a pull request, an incident, a deploy — investigates across your code, telemetry, and live control-plane state, opens a scenario-backed fix, and waits for human approval before it ships or drafts the customer reply. Runs against a durable, replayable log — posts evidenced answers, never chats. [![Docs](https://img.shields.io/badge/agentsfleet-Docs-5EEAD4?style=for-the-badge)](https://docs.agentsfleet.net) [![Get early access](https://img.shields.io/badge/agentsfleet-Get_early_access-5EEAD4?style=for-the-badge)](https://agentsfleet.net) diff --git a/index.mdx b/index.mdx index f6dcae8..39b6dfb 100644 --- a/index.mdx +++ b/index.mdx @@ -1,17 +1,17 @@ --- -title: "Your deploy failed. The agent already knows why." -description: "agentsfleet is an open runtime that owns operational outcomes — an agent wakes on your events, gathers evidence from your own systems, posts a diagnosis with proof, and keeps a replayable log of every move it made." +title: "A fleet, ready to run." +description: "agentsfleet is a fleet of prebuilt AI teammates for recurring engineering work — each one wakes on an event, gathers evidence from your own systems, opens a scenario-backed fix, and holds at human approval. Every move is a replayable log." --- - - **Stealth-mode testing.** agentsfleet is in private alpha — APIs and agent behavior may change without long deprecation windows. Want a hand calibrating an agent or to join as a design partner? Email [agentsfleet@agentmail.to](mailto:agentsfleet@agentmail.to). - + + agentsfleet is in early access. Join the waitlist to get in — or email [agentsfleet@agentmail.to](mailto:agentsfleet@agentmail.to) to come on as a design partner. + -## The 2am problem +## A teammate that owns the outcome -A deploy fails at 2am. Your on-call engineer is asleep, so someone guesses from a stack trace and ships a patch on hope. By morning the context is gone — no record of what was tried, evidence scattered across CI, logs, dashboards, and chat. +A pull request lands. A deploy fails at 2am. Normally someone guesses from a stack trace and ships a patch on hope — and by morning the context is gone, evidence scattered across CI, logs, dashboards, and chat. -agentsfleet owns the outcome instead. An **agent** is a durable runtime described in two markdown files — `SKILL.md` (the senior engineer's playbook in prose) plus `TRIGGER.md` (which tools the agent can reach and which events wake it). When a trigger fires, the agent gathers the evidence, reasons over it, posts an evidenced diagnosis to your Slack channel, and keeps a replayable log of every move it made. +A teammate owns the outcome instead. An **agent** is a durable runtime described in two markdown files — `SKILL.md` (the senior engineer's playbook in prose) plus `TRIGGER.md` (which tools the agent can reach and which events wake it). When a trigger fires, it gathers the evidence, reasons over it, opens a scenario-backed fix, posts an evidenced diagnosis to your Slack channel, and keeps a replayable log of every move — holding at human approval before anything merges or ships. The flagship `platform-ops` wakes on a GitHub Actions deploy failure, pulls workflow logs + your hosting provider's app state + your data-plane's health, and posts a one-paragraph diagnosis with a leading hypothesis. The same agent is reachable via `agentsfleet steer` for a manual investigation. The runtime is open source, you bring your own model and pay your provider directly, and the agent never sees your raw keys — only `${secrets.NAME.FIELD}` placeholders, swapped for real values outside the sandbox. From 7f86ca85f2844e22edd6ea106205f745bfb1d9af Mon Sep 17 00:00:00 2001 From: Kishore Kumar Date: Thu, 18 Jun 2026 18:30:51 +0530 Subject: [PATCH 2/3] docs: frame platform-ops as one prebuilt teammate in a growing fleet Make explicit that platform-ops is one of several prebuilt teammates (code review, incident triage, security review join the fleet), not the whole product. Co-Authored-By: Claude Opus 4.8 (1M context) --- index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.mdx b/index.mdx index 39b6dfb..fd14ce5 100644 --- a/index.mdx +++ b/index.mdx @@ -13,7 +13,7 @@ A pull request lands. A deploy fails at 2am. Normally someone guesses from a sta A teammate owns the outcome instead. An **agent** is a durable runtime described in two markdown files — `SKILL.md` (the senior engineer's playbook in prose) plus `TRIGGER.md` (which tools the agent can reach and which events wake it). When a trigger fires, it gathers the evidence, reasons over it, opens a scenario-backed fix, posts an evidenced diagnosis to your Slack channel, and keeps a replayable log of every move — holding at human approval before anything merges or ships. -The flagship `platform-ops` wakes on a GitHub Actions deploy failure, pulls workflow logs + your hosting provider's app state + your data-plane's health, and posts a one-paragraph diagnosis with a leading hypothesis. The same agent is reachable via `agentsfleet steer` for a manual investigation. The runtime is open source, you bring your own model and pay your provider directly, and the agent never sees your raw keys — only `${secrets.NAME.FIELD}` placeholders, swapped for real values outside the sandbox. +`platform-ops` is **one** prebuilt teammate, and more keep joining the fleet — code review, incident triage, security review. It wakes on a GitHub Actions deploy failure, pulls workflow logs + your hosting provider's app state + your data-plane's health, and posts a one-paragraph diagnosis with a leading hypothesis. The same agent is reachable via `agentsfleet steer` for a manual investigation. The runtime is open source, you bring your own model and pay your provider directly, and the agent never sees your raw keys — only `${secrets.NAME.FIELD}` placeholders, swapped for real values outside the sandbox. ## Get started From 328cc2e9cc5b2331c76c2f13015e3817a2bf5b10 Mon Sep 17 00:00:00 2001 From: Kishorekumar Neelamegam Date: Thu, 18 Jun 2026 20:39:32 +0530 Subject: [PATCH 3/3] Update README.md Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7922863..4a39221 100644 --- a/README.md +++ b/README.md @@ -11,7 +11,7 @@ Each one wakes on an event — a pull request, an incident, a deploy — investigates across your code, telemetry, and live control-plane state, opens a scenario-backed fix, and waits for human approval before it ships or drafts the customer reply. Runs against a durable, replayable log — posts evidenced answers, never chats. [![Docs](https://img.shields.io/badge/agentsfleet-Docs-5EEAD4?style=for-the-badge)](https://docs.agentsfleet.net) -[![Get early access](https://img.shields.io/badge/agentsfleet-Get_early_access-5EEAD4?style=for-the-badge)](https://agentsfleet.net) +[![Get early access](https://img.shields.io/badge/agentsfleet-Get_early_access-5EEAD4?style=for-the-badge)](https://accounts.agentsfleet.net/waitlist) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg?style=for-the-badge)](https://opensource.org/licenses/MIT)