Skip to content
InfratoApp
Layers / Orchestration / Agents / Agent frameworks / fyagent

fyagent

UNCLAIMED

AGENT FRAMEWORKS

fyagent — For You Agent——AI 时代的个人随身数字人格。把你的模型、AI 账号、技能、提示词和工作方式,带到每一个 AI 工具里。. Listed under Agent frameworks in the Orchestration / Agents layer. 1 of 9 comparison attributes are recorded, each with the page it was read from.

FyAgent v0.4.10 A fix release after 0.4.9 focused on Windows installation and detection. The issues were found during the v0.4.9 virtual machine installer smoke runs. Fixes Claude Code and Grok Bu...

3 OF 4 SIGNALS HELD · MISSING LICENCE

Repositoryfy-agent/fyagent

What it runs on, and what runs on it

0 cited edges
The differentiator

Computed from the stack graph, both directions. Every cited edge links the page it was read from; a vendor-added one links the vendor’s own source — this is the reason to be here rather than on the vendor’s own site.

No edges on record for fyagent.

Nothing in the directory documents depending on it, and its own docs do not name what it runs on. An edge is only stored when a source states it.

Submit a documented integration →

Open-source signals

LICENCE
not measured
DOWNLOADS 30D
not measured
LAST COMMIT
not measured

A HOLLOW RING IS UNMEASURED, NOT ZERO · WE DO NOT SUBSTITUTE A PARENT COMPANY’S REPOSITORY FOR A PRODUCT THAT HAS NONE

Price

We hold no price for this product.

Either the pricing is behind a sales call and there is no public page to read, or the last reading passed 21 days and was hidden rather than shown stale. If that changes — or if you publish /.well-known/pricing.json — it appears here with a capture date.

How we read prices →

What its categories ask

1 answered · 8 unanswered

9 questions declared by Agent frameworks. Most rows across the directory read like these.

ATTRIBUTEANSWEREVIDENCE · SOURCE
LicenceNotSigned
“The installer rows below are backed by the published signing-status.json and artifact-attestation.sigstore.json evidence. Architecture Installer Authenticode Publisher Timestamp SHA-256 Source SHA Attestation x64 FyAgent-0.4.10-Windows-x64-setup.exe NotSigned Not signed None 627959e3d6e8ceb8ff0aa226”
2026-10-13
Durable executionno answer on record
Human in the loopno answer on record
MCP serverno answer on record
Memory typesno answer on record
Multi-agentno answer on record
Open sourceno answer on record
SDK languagesno answer on record
Tool callingno answer on record

A ROW WITH NO ANSWER IS NOT A ROW WITH A “NO” · A VENDOR MAY ANSWER A BLANK ONE, MARKED VENDOR CLAIMED WITH ITS SOURCE · A DOCUMENTED VALUE IS DISPUTED, NOT OVERWRITTEN, AND STAYS VISIBLE WHILE WE RE-READ THE SOURCE

Practitioner reviews

Nobody has written one yet.

A review here is structured, not a star: hardware, scale band, what broke in production, and whether you would choose it again.

NO PERCENTAGE IS SHOWN UNDER FIVE REVIEWS · NO STAR RATINGS, EVER

Also in this category

103 products in Agent frameworks. Comparison defaults to within the category — pairing this with a GPU cloud would produce a page that means nothing.

USED BY = LISTED PRODUCTS DEPENDING ON IT, IN THIS DIRECTORY

Frequently asked

What does a blank mean on the fyagent page?
That nobody has told us, not that the answer is no. A hollow ring is "no answer on record", which is a different state from a recorded no — and the two look different on purpose. A blank is an absence of evidence, and this page shows how many of its questions are in that state rather than quietly leaving them out.
Where do the fyagent figures come from?
Each one is read from a public page — usually the vendor's own documentation or pricing page — and carries a link to it with the date it was read. Nothing here is estimated, averaged across sources, or inferred from a similar product. If a figure cannot be traced to a page, it is not published.
Can fyagent change what this page says?
They can claim the listing and supply or correct values, which are then labelled as theirs. They cannot remove the page, hide a comparison they are losing, or change a figure somebody else recorded with a source. Nothing on the page is for sale. How the site is paid for is set out under money and independence at /our-data#sec5.
Something here is wrong — how do I fix it?
Dispute the value. Every figure links to the page it was read from, so a dispute names the value and gives a source that contradicts it. That is the only lever anyone has over this page, and it is the same lever for the vendor, a competitor and a reader.

Cite this page

A model that quotes us should quote us correctly. The reading and its date sit inside the citation rather than beside it, because a quotation carrying only a URL goes wrong the week the URL changes.

infratoapp, “fyagent — Agent frameworks”, read 13 October 2026. Licence: NotSigned as published at github.com. https://www.infratoapp.com/products/fyagent

What fyagent can and cannot change here

Claiming the organisation lets its admins and editors change the tagline, description, logo, docs link and deployment model of every product that org owns — live, labelled as theirs, and logged. Answers to blank questions and dependencies go live too, marked as the owner’s and sourced; a documented answer cannot be overwritten. Everything else on this page is a stated fact with a dispute route: price, licence and OSS figures. Those columns are ungranted at the database level, so they are not a feature we withheld — they are a write that cannot happen. Name, category, website, pricing page and package names can be changed by the owner only through our review. A dispute never deletes a value; it marks it and publishes the correction.