From 4e34cc4e28dd0757c31958251bdfc6fe89709dad Mon Sep 17 00:00:00 2001 From: EngineerProjects Date: Mon, 22 Jun 2026 19:43:33 +0200 Subject: [PATCH 1/2] =?UTF-8?q?docs(readme):=20add=20motivation=20intro=20?= =?UTF-8?q?=E2=80=94=20why=20Go,=20the=20team-agent=20gap,=20and=20the=20t?= =?UTF-8?q?hesis?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Tagline updated: 'Built for the age of agent teams, not just single agents' - Navigation links: Discussions Β· Issues Β· seshat-ai - New intro section 'Why Seshat': - Go vs Python agent frameworks: single binary, no deps, production-grade - The real gap: individual agents are solved, team collaboration is not - The thesis: model human organizational work (roles, inboxes, meetings, reports, mission memory) to reproduce it with autonomous agents - Current state and roadmap direction - Open invitation to the community (Discussions, issues, PRs) --- README.md | 50 +++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 49 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 31289b9..ccbf53e 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,13 @@

Open-source Go runtime for AI agents
- One runtime. Any LLM. Any language. Any deployment. + Built for the age of agent teams, not just single agents. +

+ +

+ πŸ’¬ Discussions Β· + πŸ› Issues Β· + πŸ–₯️ seshat-ai

@@ -19,6 +25,48 @@ --- +## Why Seshat + +The agentic AI space is moving fast. Dozens of frameworks have emerged β€” LangChain, LangGraph, CrewAI, AutoGen, and many others. Almost all of them are Python-first. That works fine for experimentation, but it creates real friction the moment you want to ship something: dependency hell, slow startup, heavy containers, difficult embedding in existing services. + +**Go changes the equation.** A single statically linked binary. No runtime, no venv, no dependency manager. Low latency, predictable memory, easy deployment anywhere β€” from a Raspberry Pi to a Kubernetes cluster. Seshat brings that to agentic AI. + +But the choice of language is the smaller part of the story. + +--- + +### The real gap: agents don't know how to work together + +Individual agents have become impressive. They can reason for hours, use tools, write code, search the web, produce deliverables. The frontier has moved. The hard unsolved problem is no longer *what a single agent can do* β€” it is **how multiple agents can work together in a coherent, observable, and economically useful way**. + +Most current systems handle this with pipelines, handoffs, or orchestration graphs. These are useful, but they remain technical constructs. They don't model *work* the way humans actually do it. + +--- + +### The thesis behind this project + +We believe the right model for agent collaboration is not the workflow graph β€” it is the **human organization**. + +Real teams don't communicate through function calls. They have roles, responsibilities, inboxes, meetings, status reports, shared decisions, and a working memory of the mission. A project lead delegates tasks. A specialist delivers a report. A reviewer pushes back. A coordinator synthesizes. Information flows explicitly. Decisions are recorded. Nothing is lost in a black-box state machine. + +Seshat is being built around this idea: **study how humans work in teams β€” in companies, research groups, or any collaborative setting β€” and reproduce those coordination patterns with autonomous agents.** + +This means agents that communicate through structured messages, not just function calls. Agents that can send a report, schedule a review, claim a task, escalate a blocker, or update a shared mission memory. Agents that have an identity, a role, and a history β€” not just a prompt and a response. + +--- + +### Where we are and where we're going + +We are building the foundation. Seshat today is a solid, production-grade runtime: persistent sessions, 60+ tools, 15 LLM providers, MCP client, RAG, skills, gRPC API, sandboxed execution. It is already useful as a standalone CLI, an embeddable Go SDK, or the engine behind [seshat-ai](https://github.com/EngineerProjects/seshat-ai). + +The team primitives β€” mailboxes, roles, missions, structured inter-agent communication β€” are the next major layer. We are designing them now, informed by how real organizations function. + +**This is an open research and engineering project as much as a software one.** If you have ideas about how agents should collaborate, how human team structures map to agentic systems, or what organizational patterns are worth modeling β€” your input is genuinely valuable. Open a [Discussion](https://github.com/EngineerProjects/seshat/discussions), an issue, or a PR. + +We are building this together. + +--- + ## πŸ–₯️ Terminal UI `seshat chat` drops you into a full-featured terminal interface built for long-running agent sessions. From 26509699aa00e08f879312a1b606aadbed547958 Mon Sep 17 00:00:00 2001 From: EngineerProjects Date: Mon, 22 Jun 2026 19:47:03 +0200 Subject: [PATCH 2/2] docs(readme): add emojis to intro section --- README.md | 28 ++++++++++++++++++++-------- 1 file changed, 20 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index ccbf53e..391ddc5 100644 --- a/README.md +++ b/README.md @@ -25,17 +25,17 @@ --- -## Why Seshat +## πŸ€” Why Seshat The agentic AI space is moving fast. Dozens of frameworks have emerged β€” LangChain, LangGraph, CrewAI, AutoGen, and many others. Almost all of them are Python-first. That works fine for experimentation, but it creates real friction the moment you want to ship something: dependency hell, slow startup, heavy containers, difficult embedding in existing services. -**Go changes the equation.** A single statically linked binary. No runtime, no venv, no dependency manager. Low latency, predictable memory, easy deployment anywhere β€” from a Raspberry Pi to a Kubernetes cluster. Seshat brings that to agentic AI. +**⚑ Go changes the equation.** A single statically linked binary. No runtime, no venv, no dependency manager. Low latency, predictable memory, easy deployment anywhere β€” from a Raspberry Pi to a Kubernetes cluster. Seshat brings that to agentic AI. But the choice of language is the smaller part of the story. --- -### The real gap: agents don't know how to work together +### 🚧 The real gap: agents don't know how to work together Individual agents have become impressive. They can reason for hours, use tools, write code, search the web, produce deliverables. The frontier has moved. The hard unsolved problem is no longer *what a single agent can do* β€” it is **how multiple agents can work together in a coherent, observable, and economically useful way**. @@ -43,7 +43,7 @@ Most current systems handle this with pipelines, handoffs, or orchestration grap --- -### The thesis behind this project +### 🧠 The thesis behind this project We believe the right model for agent collaboration is not the workflow graph β€” it is the **human organization**. @@ -51,19 +51,31 @@ Real teams don't communicate through function calls. They have roles, responsibi Seshat is being built around this idea: **study how humans work in teams β€” in companies, research groups, or any collaborative setting β€” and reproduce those coordination patterns with autonomous agents.** -This means agents that communicate through structured messages, not just function calls. Agents that can send a report, schedule a review, claim a task, escalate a blocker, or update a shared mission memory. Agents that have an identity, a role, and a history β€” not just a prompt and a response. +This means agents that: +- πŸ“¬ communicate through structured messages, not just function calls +- πŸ“‹ can send a report, schedule a review, claim a task, or escalate a blocker +- 🧩 have an identity, a role, and a history β€” not just a prompt and a response +- πŸ—‚οΈ share a mission memory that keeps decisions, constraints, and objectives alive across the team --- -### Where we are and where we're going +### πŸ—ΊοΈ Where we are and where we're going We are building the foundation. Seshat today is a solid, production-grade runtime: persistent sessions, 60+ tools, 15 LLM providers, MCP client, RAG, skills, gRPC API, sandboxed execution. It is already useful as a standalone CLI, an embeddable Go SDK, or the engine behind [seshat-ai](https://github.com/EngineerProjects/seshat-ai). The team primitives β€” mailboxes, roles, missions, structured inter-agent communication β€” are the next major layer. We are designing them now, informed by how real organizations function. -**This is an open research and engineering project as much as a software one.** If you have ideas about how agents should collaborate, how human team structures map to agentic systems, or what organizational patterns are worth modeling β€” your input is genuinely valuable. Open a [Discussion](https://github.com/EngineerProjects/seshat/discussions), an issue, or a PR. +--- + +### 🀝 An open project β€” all ideas welcome + +**This is an open research and engineering project as much as a software one.** The ecosystem we want to build is ambitious, and no single perspective has all the answers. + +If you have ideas about how agents should collaborate, how human team structures map to agentic systems, what organizational patterns are worth modeling, or what the ecosystem is still missing β€” your input is genuinely valuable. + +πŸ‘‰ Open a [Discussion](https://github.com/EngineerProjects/seshat/discussions), an issue, or a PR. Every suggestion is read. -We are building this together. +We are building this together. πŸš€ ---