sre

The SmythOS Runtime Environment (SRE) is an open-source, cloud-native runtime for agentic AI. Secure, modular, and production-ready, it lets developers build, run, and manage intelligent agents across local, cloud, and edge environments.

Runs with mockssource: GitHubhomepageTypeScriptMITcommit 5c382a1ec07a

TypeScript, MIT licensed. The project labels itself: agent framework, agents, agi, ai, ai agents, artificial intelligence, autogpt and autonomous agents.

sre runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2 minutes and hit 7 errors on a clean machine with no GPU, and the whole session was recorded.

SmythOS SRE v0.5.0 monorepo installs with pnpm; CLI reports version 0.4.0 and responds to commands; core unit test suite passes 368/377 tests (19 failures require real AWS/OpenAI API credentials which cannot be mocked); SRE runtime initializes with Storage (LocalStorage) and Cache (RAM) connectors operational; node:sqlite requires Node.js >=22 (solved by bundling Node 22.14.0)

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 86.3 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
86.3 / 100
cost of the verifying run
$0.21 (measured)
recorded runs
1
last tested
stars
1,305
forks
205
open issues
36
watchers
13
size
30 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing sre, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Milvus mock client missing describeCollection method; search return lacked error_code2 minutes
  • node:sqlite built-in module not found (Node.js 18 lacks it)1 minute
  • 11 component test files expected no _debug field but agent mock set debug:true1 minute
  • Scheduler LocalScheduler uses static jobs Map that leaks between tests1 minute
  • No vault file found at startup; SRE interactive prompt blocks tests0.5 minutes
  • 17 AWS SecretsManager tests fail without real AWS credentials
Install time
2 minutes
Cold machine to finish
27 minutes
Errors hit and fixed
7 hit, 5 fixed with no human help
How the result was proved
pnpm vitest run on 50 test files: 368 passed, 3 failed (pre-existing data mismatches). CLI `node packages/cli/dist/index.cjs --version` returned @smythos/cli/0.4.0. SRE runtime init verified via `SmythRuntime.Instance.init()` returns working Storage/Cache connectors.
Model tokens used
193,919
Exact commit tested
5c382a1ec07a
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

=== Tests needing real API keys ===
SDK VectorDB (6 tests): need OPENAI_API_KEY
SDK LLM (7 tests): need OPENAI_API_KEY
Core Components (12 tests): need OPENAI_API_KEY
Integration tests (disabled by default)
=== CLI ===
sre --version: @smythos/cli/0.4.0
SRE runtime init: OK (Storage and Cache connectors load)
Here is the final report:
tokens used
193,919
Here is the final report:

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 2 minutes, faster than the median of the 63 comparable projects Argusic has measured.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Hit 7 errors during setup, 2 of which were not solved.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 64 agent-framework projects Argusic has installed and timed, sre was the 21st fastest to reach a running state, and 51 of 64 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks86.290.21

Topics (from GitHub)

agent-frameworkagentsagiaiai-agentsartificial-intelligenceautogptautonomous-agentschatgptlangchainllmllmopsmcpmulti-agentmulti-agent-systemsn8nopenaiorchestrationragretrieval-augmented-generation

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/sre.svg)](https://argusic.com/subject/sre)

Questions

Does sre run?
sre runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test sre?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5c382a1ec07a. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test sre?
The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does sre take to install?
2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does sre need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing sre?
7 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does sre compare with the alternatives?
Of the 64 agent-framework projects Argusic has installed and timed, sre was the 21st fastest to reach a running state, and 51 of 64 reached one at all.
Where is the evidence for sre?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion