temporal
Temporal service
Runssource: GitHubhomepageGoMITcommit d8f9c6d86b2c
Go, MIT licensed. The project labels itself: cronjob scheduler, distributed cron, distributed systems, durable execution, golang, microservice framework, microservice orchestration and microservices architecture.
temporal runs. An Argusic agent installed it in 28.2 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Temporal server 1.33.0 builds from source with Go 1.27.0, starts with SQLite in-memory persistence, exposes gRPC on 4 ports (frontend:7233, history:7234, matching:7235, worker:7239), responds SERVING on health check, and launches system workflows. 5 binaries built. Core unit 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.
- Some test suites (ScaleManagerSuite, MatchingEngine, TaskQueuePartitionManager) hang when run together in ./service/matching/8 minutes
- Makefile unit-test target fails: -race flag requires cgo, but Makefile defaults CGO_ENABLED=05 minutes
- Go 1.27.0 not installed in container2 minutes
- make lint-code-fast requires main branch for diff base1 minute
- Install time
- 28 minutes
- Cold machine to finish
- 55 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- go build ./cmd/server/ exit 0; make bins exit 0; ./temporal-server --version returned 'temporal version 1.33.0'; server started with 4 gRPC listeners on ports 7233/7234/7235/7239; grpc health check returned SERVING; go test passed on common/{backoff,cache,config,definition,dynamicconfig,headers,health,locks,metrics,quotas,rpc,serviceerror,util,auth,authorization,collection,contextutil,nexus,primitives,archiver,callbacks,checksum,cluster,codec,failure,future,searchattribute,telemetry}, client/{history,matching}, service/{frontend,history}, service/matching/{forwarder,ack,backlog,matcher,physical_task_queue_manager} suites individually
- Model tokens used
- 405,321
- Exact commit tested
- d8f9c6d86b2c
- 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.
ok go.temporal.io/server/temporal 10.815s ok go.temporal.io/server/temporaltest 6.179s exec /bin/sh -lc 'pkill -P 50409 2>/dev/null; sleep 1; echo "done"' in /work/repo succeeded in 870ms: done Now I have all the data. Here's the final assessment: 2026-09-25T20:11:14.199878Z ERROR codex_core::session: failed to record rollout items: thread 01a0d… 2026-09-25T20:11:14.200048Z ERROR codex_core::session: failed to record rollout items: thread 01a0d… tokens used 405,321 Now I have all the data. Here's the final assessment:
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 28.2 minutes.
- 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 MIT, 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)
cronjob-schedulerdistributed-crondistributed-systemsdurable-executiongolangmicroservice-frameworkmicroservice-orchestrationmicroservices-architectureorchestratorservice-busservice-fabricworkflow-automationworkflow-engineworkflow-managementworkflow-management-systemworkflows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/temporal)Questions
- Does temporal run?
- Yes. temporal runs. Argusic installed and launched it on a clean machine in 28 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test temporal?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d8f9c6d86b2c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test temporal?
- The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does temporal take to install?
- 28.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 temporal need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing temporal?
- 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 temporal?
- 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.