NearBeach
NearBeach is an open sourced project management tool, helping you keep track of your project. You can track requirements, projects and tasks
Runssource: GitHubhomepageCSSMITcommit dd051a04714a
CSS, MIT licensed. The project labels itself: django, django application, open source, opensource, project management, python and python3.
NearBeach runs. An Argusic agent installed it in 6 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
NearBeach project management system installed and fully functional. Python Django backend and JavaScript Vue.js frontend both build and pass all tests without errors.
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 100 of 100 (the mean of this project's run scores).
At a glance
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.
- Install time
- 6 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- Django test suite: 114 tests passed (OK). Vitest frontend: 169 files, 172 tests passed. Django dev server starts and responds HTTP 302 on GET /.
- Model tokens used
- 75,250
- Exact commit tested
- dd051a04714a
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
--- Django test count ---
Ran 114 tests in 72.036s
exec
/bin/sh -lc 'cd /work/repo && . venv/bin/activate && python -m django test NearBeach.tests --settin…
I have all the data I need. Let me compile the final result.
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 2, "errors": [], "test_dep…
2026-10-30T03:36:46.216363Z ERROR codex_core::session: failed to record rollout items: thread 01a18…
tokens used
75,250Replay 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
- Reached a running state on a clean machine, with the session recorded.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 6 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 6 django projects Argusic has installed and timed, NearBeach was the 4th fastest to reach a running state, and 5 of 6 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 6 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Run history
Topics (from GitHub)
djangodjango-applicationopen-sourceopensourceproject-managementpythonpython3
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/nearbeach)Questions
- Does NearBeach run?
- Yes. NearBeach runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test NearBeach?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dd051a04714a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test NearBeach?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does NearBeach take to install?
- 6 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 NearBeach need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing NearBeach?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does NearBeach compare with the alternatives?
- Of the 6 django projects Argusic has installed and timed, NearBeach was the 4th fastest to reach a running state, and 5 of 6 reached one at all.
- Where is the evidence for NearBeach?
- 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.