django-helpdesk
A Django application to manage tickets for an internal helpdesk. Formerly known as Jutda Helpdesk.
Runssource: GitHubPythonBSD-3-Clausecommit a3d61c598a72
Python, BSD-3-Clause licensed. The project labels itself: agile, bugs, cases, django, hacktoberfest, hacktoberfest2020, helpdesk and incidents.
django-helpdesk runs. An Argusic agent installed it in 3 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
django-helpdesk demo server starts on port 8080, public portal returns HTTP 200, admin dashboard returns HTTP 200 after login, and all 430 tests pass.
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- `uv` not found in environment1 minute
- `yarn` not found in environment1 minute
- yarn@1 refused to run due to packageManager: [email protected] field in package.json0.5 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- curl http://localhost:8080/ returned 200; admin login at /admin/ returned 200 after POST auth; python quicktest.py: OK (Ran 430 tests)
- Model tokens used
- 28,151
- Exact commit tested
- a3d61c598a72
- 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.
**Errors encountered:** 1. `uv` not installed → fixed by curl-installing it 2. `yarn` not installed → fixed by npm-installing it to `$HOME/.local` 3. yarn 1 refused to run because `packageManager: [email protected]` → fixed by removing that field from `… 4. `yarn install` warned about missing `@popperjs/core` peer dependency for bootstrap → non-fatal w… exec /bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 3… succeeded in 0ms: {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 3, "errors": [{"msg": "`uv… 2026-11-13T22:18:33.139012Z ERROR codex_core::session: failed to record rollout items: thread 01a1d… tokens used 28,151
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
- Reached a running state on a clean machine, with the session recorded.
- Installed in 3 minutes, faster than the median of the 4 comparable projects Argusic has measured.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed BSD-3-Clause, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 5 agile projects Argusic has installed and timed, django-helpdesk was the 1st fastest to reach a running state, and 4 of 5 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 3 minutes after the clone.
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
Topics (from GitHub)
agilebugscasesdjangohacktoberfesthacktoberfest2020helpdeskincidentsissueskanbanpythonscrumservicedesksupportticketstracker
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/django-helpdesk)Questions
- Does django-helpdesk run?
- Yes. django-helpdesk runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test django-helpdesk?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a3d61c598a72. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test django-helpdesk?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does django-helpdesk take to install?
- 3 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 django-helpdesk need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing django-helpdesk?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does django-helpdesk compare with the alternatives?
- Of the 5 agile projects Argusic has installed and timed, django-helpdesk was the 1st fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for django-helpdesk?
- 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.