agent-substrate/substrate: README-based editorial guide
A guide grounded in the README, repository metadata, and license for installing and checking agent-substrate/substrate.
Project scope
agent-substrate/substrate describes itself in the README as "Agent Substrate: the core system". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "Agent Substrate", the README says: NOTE: This is not an officially supported Google product. This project is not eligible for the Google Open Source Software Vulnerability Rewards Program.. That establishes the project's stated boundary, not a production test.
Suitable use cases
The README's "Framework Agnostic & Compatibility" section gives a useful starting point for deciding whether the project fits: LangChain: Ideal execution environment for long-running, stateful LangChain agents and sandboxed tool-calling.. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Agent Development Kit (ADK): Native support for ADK-compatible actor identity and persistent working memory.. It can shape a first test, but it does not replace testing in the intended environment.
How it works
The operating model is spread across sections such as "What is Agent Substrate?". The source evidence includes: At its core, Agent Substrate maps a larger set of "actors" (applications such as agents) onto a smaller set of ready "workers", relying on the fact that agent-like applications tend to be idle most of the time to achieve heavy multiplexing.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.
Installation and first run
Start installation from the README's documented entry point. A command that can be checked in the source is: # create cluster and local registry hack/create-kind-cluster.sh # install ate, valkey, rustfs hack/install-ate-kind.sh --deploy-ate-system # install counter demo hack/install-ate-kind.sh --deploy-demo-counter # install kubectl-ate go install ./cmd/kubectl-ate # create an atespace (required before creating actors), then a counter actor in it kubectl ate create atespace demo kubectl ate create actor my-counter-1 -a demo --template=ate-demo-counter/counter # port-forward the network router to When the README contains no runnable command, this article does not invent one. Open its "What is Agent Substrate?" section and confirm system dependencies, default ports, and first-run initialization before using a public server.