flagsmith runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 6 errors on the way, and recorded the session.

How did Argusic test flagsmith?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 78e3fd06ce43. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test flagsmith?

The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does flagsmith take to install?

1.5 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 flagsmith need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing flagsmith?

6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for flagsmith?

All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

flagsmith

Flagsmith is an open-source feature flag platform with remote config, experimentation, and self-hosted or cloud deployment options.

Runs with mockssource: GitHub homepagePythonBSD-3-Clausecommit 78e3fd06ce43

Python, BSD-3-Clause licensed. The project labels itself: cd, ci, continuous integration, docker, feature flag, feature flaggers, feature flagging and feature flags.

flagsmith runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1.5 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Python API dependencies installed via uv, Django checks pass with custom SQLite backend, 41 API unit tests pass, 719 frontend unit tests pass, npm postinstall env config resolves correctly; full PostgreSQL/ClickHouse dependent test suite cannot run without Docker database services
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 92 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs with mocks
Argusic Score: 92 / 100
cost of the verifying run: $0.32 (measured)
recorded runs: 2
last tested: 2026-09-29
stars: 6,582
forks: 578
open issues: 725
watchers: 35
size: 368 MB
created: 2018-06-05
last push: 2026-09-28

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-29. 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 flagsmith, 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.

No Docker or PostgreSQL in container; API requires Postgres for full test suite5 minutes
app_analytics migration 0007 uses RenameIndex which fails on SQLite (ValueError: wrong number of indexes)3 minutes
ExperimentComputation(models.Model, Generic[SummaryT]) raises TypeError on Python 3.12: Cannot inherit from plain Generic3 minutes
app_analytics migration 0008 uses PostgreSQL DO block in RunSQL which fails on SQLite2 minutes
django.contrib.sites table missing with faked migrations; causes errors in helper tests2 minutes
npm run typecheck reports 6 TypeScript errors in frontend

Install time: 2 minutes
Cold machine to finish: 40 minutes
Errors hit and fixed: 6 hit, 6 fixed with no human help
How the result was proved: npx jest exited 0, 52 suites/719 passed in frontend; uv run pytest tests/unit/api/ -- 41 passed 0 failed in backend; uv run python manage.py check -- Django system check OK (2 warnings only)
Model tokens used: 232,706
Exact commit tested: 78e3fd06ce43
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.

=== Time ===
Tue Sep 29 00:22:51 UTC 2026
exec
/bin/sh -lc 'cd /work/repo && cp api/app_analytics/migrations/0007_rename_environment_id_created_at…
 succeeded in 0ms:
restored original migration
Here's the complete summary:
**Time elapsed**: ~32 minutes from start to final tests.
tokens used
232,706
Here's the complete summary:
**Time elapsed**: ~32 minutes from start to final tests.

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 1.5 minutes.
Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
Licensed BSD-3-Clause, as reported by its host.
Measured 2 times, so the result is not a one-off.

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.

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 by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Runs with mocks	92.00	0.32	2026-09-29 00:23 UTC
Argusic Runner	1/3	Ran out of time	0.00	0.22	2026-09-28 23:43 UTC

Topics (from GitHub)

cd ci continuous-integration docker feature-flag feature-flaggers feature-flagging feature-flags feature-management feature-toggles flagsmith hacktoberfest multivariate-testing python react remote-config remote-control self-hosted

Embed the badge

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

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

Questions

Does flagsmith run?: flagsmith runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test flagsmith?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 78e3fd06ce43. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test flagsmith?: The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does flagsmith take to install?: 1.5 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 flagsmith need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing flagsmith?: 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for flagsmith?: All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.