Agently

[GenAI Application Development Framework] 🚀 Build GenAI application quick and easy 💬 Easy to interact with GenAI agent in code using structure data and chained-calls syntax 🧩 Use Event-Driven Flow *TriggerFlow* to manage complex GenAI working logic 🔀 Switch to any model without rewrite application code

Runssource: GitHubhomepagePythonApache-2.0commit d58239501e7d

Python, Apache-2.0 licensed. The project labels itself: agent, agent based framework, agent framework, chatglm, claude, deepseek, ernie and framework.

Agently runs. An Argusic agent installed it in 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.

Agently 4.1.4.8 installs and runs from a Python virtual environment; 2736 tests pass covering Agent execution, Actions, TaskBoard, TriggerFlow, Shell, RecordStore, Skills, Code execution, structured output, long-output continuation, compatibility registry, and context contracts.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.23 (measured)
recorded runs
2
last tested
stars
1,673
forks
187
open issues
22
watchers
23
size
51 MB
created
last push

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.

Time lost to each failure while testing Agently, 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.

  • TrustedLocalExecutionResourceProvider used shutil.which('python') which found nothing3 minutes
  • PythonCodeRuntimeAdapter used 'python' as subprocess argv but only 'python3' exists on this Debian system2 minutes
  • gVisor test didn't mock is_binary_available, Docker not available1 minute
  • Missing python-dotenv dependency for .env file loading0.5 minutes
Install time
2 minutes
Cold machine to finish
16 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
python -m pytest ignoring characterization, cores, integrations, utils returned 2736 passed, 39 skipped
Model tokens used
371,831
Exact commit tested
d58239501e7d
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

4. `test_gvisor_execution_provider.py::test_gvisor_direct_docker_run_emits_one_fixed_runtime_argv` …
**Remaining failures (9)**: All in `test_agent_execution_characterization.py` — these compare curre…
tokens used
371,831
Here is the final report:
**Install**: Created venv, pip-installed with all dependencies. Install succeeded.
**Errors found and fixed**:
1. Missing `python-dotenv` — `Settings.py` tried to `import dotenv` for `.env` file loading. Instal…
2. `PythonCodeRuntimeAdapter` used `"python"` as argv binary but only `python3` exists on this Debi…
3. `TrustedLocalExecutionResourceProvider._tool_facts` used `shutil.which("python")` which found no…
4. `test_gvisor_execution_provider.py::test_gvisor_direct_docker_run_emits_one_fixed_runtime_argv` …
**Remaining failures (9)**: All in `test_agent_execution_characterization.py` — these compare curre…

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 2 minutes, faster than the median of the 138 comparable projects Argusic has measured.
  • 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.
  • Measured 2 times, so the result is not a one-off.

Of the 139 agent projects Argusic has installed and timed, Agently was the 32nd fastest to reach a running state, and 93 of 139 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 2 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.23
Argusic Runner1/3Runs100.000.32

Topics (from GitHub)

agentagent-based-frameworkagent-frameworkchatglmclaudedeepseekernieframeworkgeminigoogle-geminigptllm-agentllm-applicationllm-appsllm-frameworkllmopsllmsminimaxpython

Embed the badge

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

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

Questions

Does Agently run?
Yes. Agently runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test Agently?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d58239501e7d. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test Agently?
The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Agently take to install?
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 Agently need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Agently?
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.
How does Agently compare with the alternatives?
Of the 139 agent projects Argusic has installed and timed, Agently was the 32nd fastest to reach a running state, and 93 of 139 reached one at all.
Where is the evidence for Agently?
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.

Discussion