RepoRadar
Leave a Tip
Item detail
github.com

agno-agi/agno

agno-agi/agno is a developer tool that RepoRadar is tracking in its Agent Frameworks section, currently rated Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 9.8 out of 10.

Open on GitHub →Back to radar
Score8.3
Popularity93.0
Riskconditional
TierGold
Score breakdown
Usefulness9.0
Novelty7.0
Momentum8.0
Maturity8.4
Open-source/build8.4
Evidence7.2
Workflow potential9.8
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

For teams moving from experiments to production agent systems, Agno provides a coherent structure for tool use, orchestration, and guardrails instead of gluing ad hoc scripts together.

Who should use it

backend builders automation teams enterprise developers agent platform builders

Who should skip it

Skip agno-agi/agno if the source link, documentation, or setup requirements do not align with your current workflow or stack.

About this signal

agno-agi/agno is tracked by RepoRadar as a developer tool in the Agent Frameworks section. First seen 2026-06-18; the source record was last checked on 2026-06-18. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for agno-agi/agno are workflow potential (9.8) and practical usefulness (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The agno-agi/agno record combines a 8.3/10 composite score with separate popularity (93.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

agent tools can access external APIs and files when configured with broad credentials; custom workflows can invoke code execution in connected environments.

Evidence links
Closest alternatives / related signals
agents framework python orchestration tool-calling
Verification record

What RepoRadar actually verified

Tested in a bounded workflow

Bounded representative workflow retained by RepoRadar verification harness. Last checked 2026-07-13T10:36:50.099796Z.

passed · cohort-20260712-agno-local-multistep-workflow

Tester
RepoRadar automated local verification harness
Started
2026-07-13T10:36:46.810453Z
Completed
2026-07-13T10:36:50.099796Z
Environment
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
1 minute(s)
Evidence scope
Bounded representative workflow
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
  • Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
  • Created 1 synthetic fixture file(s) inside the disposable work directory; retained hashes prove the exact inputs.
  • Defined classify and assign Agno Step executors and composed them into a telemetry-disabled Workflow.
  • Ran severity 4 through both steps, asserted page/on-call output, and retained the workflow name and step count.
  • Executed bounded check: Execute a two-step Agno workflow that classifies and assigns a synthetic incident.
  • Captured the complete sanitized stdout, stderr, exit status, artifact checks, and 3.29-second wall time.
Observed results
  • Command exited 0 after 3.29 seconds.
  • Agno propagated the input through two named steps and returned the combined page/on-call decision.
  • Expected marker 'CHECK_OK route=page owner=oncall steps=2' was observed in retained output.
  • Validated result.json: 4 required marker(s) present and 0 excluded marker(s) absent; size and SHA-256 are retained.
Observed strengths
  • The workflow engine executed structured sequential dataflow with explicit StepOutput handoff and no provider dependency.
Friction
  • The workflow module currently needs FastAPI installed even for this non-server path, so the isolated command includes that dependency explicitly.
  • Setup or runtime emitted 3 stderr line(s); the complete warnings/errors are preserved in the retained log.
Limitations
  • The deterministic step executors validate workflow dataflow, not an Agent, Team, model, durable database, human review, streaming, or remote execution.
  • This credential-free disposable workflow does not establish production scale, model quality, reliability under sustained use, or team adoption.

Pricing assessment: The two-step workflow ran locally with telemetry disabled and no Agno platform, model, or database service.

Privacy assessment: A synthetic severity and route existed only in the disposable local workflow process; no agent telemetry or remote storage was enabled.

Open retained test log →

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

47 dated snapshots retained from 2026-06-18 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.3 current · +0.0 net
Repository momentum9.6 current · +1.6 net
GitHub stars (observed)41,692 current · +538 net
GitHub stars41,692 exact observation
Versionv2.9.0
Last release2026-08-13T12:08:15Z
Maintenanceactive
Current riskconditional
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.39.641,692conditionaltry nowactive
2026-08-128.39.641,681conditionaltry nowactive
2026-08-118.39.641,659conditionaltry nowactive
2026-08-108.39.341,645conditionaltry nowactive
2026-08-098.39.641,636conditionaltry nowactive
2026-08-088.39.641,625conditionaltry nowactive
2026-08-078.39.641,552conditionaltry nowactive
2026-08-068.38.0Not recordedconditionaltry nownot recorded
2026-08-058.38.0Not recordedconditionaltry nownot recorded
2026-08-048.39.641,552conditionaltry nowactive
2026-08-038.39.641,552conditionaltry nowactive
2026-08-028.39.341,537conditionaltry nowactive

Why the record changed

stars changed

Stars changed: 41681 → 41692.

version changed

Version changed: v3.0.0a1 → v2.9.0.

stars changed

Stars changed: 41659 → 41681.

stars changed

Stars changed: 41645 → 41659.

stars changed

Stars changed: 41636 → 41645.

stars changed

Stars changed: 41625 → 41636.

version changed

Version changed: v2.8.6 → v3.0.0a1.

stars changed

Stars changed: 41552 → 41625.

stars changed

Stars changed: 41537 → 41552.

stars changed

Stars changed: 41531 → 41537.

stars changed

Source-observed stars changed: 41528 → 41531. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 41468 → 41484.