centra-gideon-agent
The companion AI agent that learns, adapts and gets the work done no matter the task
Runssource: GitHubhomepagePythonApache-2.0commit ca531ee54708
Python, Apache-2.0 licensed. The project labels itself: agent, agent framework, agentic ai, ai and large language models.
centra-gideon-agent runs. An Argusic agent hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
From a clean checkout the standard install steps succeed on this container after user-level Rust and Node 22 installs; the gateway boots, serves the console and authenticated API, and the built Hypermid daemon answers real memory-record create and list requests.
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.
- Schema compiler mapped every unknown dataclass field to JSON type string, so valid nested hypermid config (features object, enums) failed validation and was reset to off defaults on every load25 minutes
- Hypermid host is disabled on a fresh home because its lifecycle needs a reviewed local enrollment (operator install plan) before it can start a daemon8 minutes
- System Rust and Node 22 missing; container Node was v18 and pip editable install would build the Rust daemon and the console6 minutes
- Optional extras slack_sdk not installed, so native gideonai-slack-desk bundle fails to import (non-fatal warnings; gateway still boots and serves)
- Cold machine to finish
- 47 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- .venv/bin/gideon gateway --test-mode printed GIDEON_READY; curl with Bearer token returned 200 for /, console JS (3.6MB), manifest, ui-docs.json, /api/auth/status and /api/status; python HypermidClient request memory.record.create/memory.record.list returned record objects
- Model tokens used
- 7,029,405
- Exact commit tested
- ca531ee54708
- 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.
- Install time
- the run did not report one
- 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.
echo "start 19:27 => elapsed minutes:"
echo $(( ( $(date -u +%s) - $(date -d '"'2026-10-30 19:27:00 UTC' +%s) ) / 60 ))" in /work/repo
succeeded in 0ms:
1793391252
start 19:27 => elapsed minutes:
47
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 47, "e…
Fixed files: `runtime/gideon/core/config/schema.py` (nested dataclass schema compilation). Everythi…
tokens used
7,029,405
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 47, "e…
Fixed files: `runtime/gideon/core/config/schema.py` (nested dataclass schema compilation). Everythi…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.
- Recovered from all 4 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/centra-gideon-agent)Questions
- Does centra-gideon-agent run?
- Yes. centra-gideon-agent runs. Argusic installed and launched it on a clean machine, hitting 4 errors on the way, and recorded the session.
- How did Argusic test centra-gideon-agent?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ca531ee54708. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test centra-gideon-agent?
- The run that produced this verdict cost $1.41: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- Does centra-gideon-agent need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing centra-gideon-agent?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for centra-gideon-agent?
- 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.