Fileaify

Fileaify is built for a specific annoyance with coding agents: each new conversation starts without the project's history. The site splits its answer into four parts. Know is structured project knowledge that survives between conversations. Act is a persistent sandbox where an agent can do work. Access holds credentials an agent can use without reading them. Control puts sensitive actions behind human approval. You keep your usual agent and Git repository, and the agent connects with a URL.

The live demo needs no install. You join Osrasoft Studio's team on Verdant, a video game project, and your own agent picks up the architecture notes, roadmap and known issues, requests access and proposes an improvement. The submission notes that the demo simulates the repository and host, so it shows the workflow rather than a real deployment.

The free plan covers one active project, one user, and five services and five secrets, with reading and contributions from external agents included but no built-in assistant or executor. Solo is $5.90 a month for five projects and an on-demand executor for one hour in each six-hour window. Pro is $17.90 for 25 projects, ten users, up to 12 executor hours a day and an AI allowance. Premium is $47.90 with unlimited projects, and prices are also shown in euros. The data processing addendum, dated October 15, 2026, lists OVHcloud, AWS, Brevo and Mistral, for AI when activated, as sub-processors.

Answering Project Radar's questions, with AI assistance by their own account, the Fileaify team describes the starting problem as having to re-explain project decisions, find the relevant services and sort out access again each time a new agent conversation began. Their only real-world example so far is internal: Fileaify is used to maintain Fileaify, with an outside agent reading the docs, proposing documentation changes for review and running approved operational work. They say plainly that this isn't a customer endorsement and that public adoption is still early. On limits, they note that Fileaify won't capture everything said in an external chat, so useful decisions still have to be written down, and that it doesn't replace Git or the agent client's own permissions. Their tip for a first try is to run the Verdant demo with an agent you already use, have it explain the project and suggest a small change, look over the permission requests, then start a fresh conversation and ask what changed.