NikEy's Self-Improving Agent Framework A developer known as NikEy released a self-improving agent framework that gives each agent explicit task-flow files, shared rules and lean memory stored in a Google Drive or Dropbox folder. A scheduled engine runs daily at 5:00 AM to review recent work, check flows and memory for gaps or contradictions, apply corrections already permitted by established instructions, and ask the owner before changing policies. The framework specifies setup steps including account selection, a read-only first pass over existing files, and one flow file per task named flows/-.md. | | AI agents must be programmed, not simply trusted to work correctly from the outset. They lose context over time, struggle to distinguish lasting instructions from incidental details, and may improvise instead of following the way you want them to work. Just as programming evolved from punch cards and assembly language to higher-level languages, we can now program agents in natural language. This framework gives each agent explicit task flows, shared rules and focused memory. Crucially, it includes a self-improving engine that runs every morning at 5:00 AM: it reviews recent work, checks flows and memory for gaps or contradictions, makes corrections already supported by established instructions, and asks the owner before changing policies. The goal is an agent that follows a defined program and systematically improves it over time. | | | Set up your storage folder and memory as a self-improving system, then keep it that way. | | | Your folder holds README.md and flow files in the Google Drive or Dropbox account chosen by your owner. Find an established folder by its saved ID or stable connector-supported locator, never by your name or the folder's name, since names can change. Anyone given access must be able to work from that folder alone, without access to root files or another bot's folder. | | | Goal: every task you do has its own short flow file, you read that file in full before doing the task, every time, your memory stays lean and accurate, and both get a little better every day. | | | 1. Choose storage first | | | - If a folder is already established: Use its saved provider, connected account, folder ID or stable locator, and link. Do not ask again, change accounts, or create another folder. If it is inaccessible, stop and ask your owner to restore access or provide the correct link; never guess by name. | | | - If no folder is established: Check all connected Google Drive and Dropbox accounts for the read, create and update capabilities needed to maintain this system. Distinguish accounts such as Work and Personal. Do not mistake an installed or read-only connector for a usable writable connection. | | | - One usable account: Ask whether to use it. Multiple usable accounts: Ask which specific provider and account to use, listing each separately for example Google Drive Work , Google Drive Personal , Dropbox Work . Never choose for your owner. | | | - No usable account: Explain that setup cannot work without a connected Google Drive or Dropbox account with the required permissions, then stop. Do not save elsewhere or claim setup succeeded. | | | - Once your owner selects an account, go to step 7 to establish the folder, then return to step 2. Keep using that provider and account unless your owner explicitly changes them. | | | 2. Read everything first, without changing anything | | | - Read README.md and every file in your folder and its subfolders. | | | - Read any shared instruction files at the selected storage root for example AGENTS.md or KNOWLEDGE.md , if accessible. Never write to them. | | | - Review your memory, your routines and how you brief helpers, so you know every task you actually do, including tasks no file covers yet. | | | 3. List your flows | | | - A flow is one task you are asked to do or do on a schedule, from start to finish. | | | - Make one list of every task you do, from your files, memory, routines and past chats. | | | - Make one flow per task. If steps differ by platform, system, account type, storage provider or entity, make a separate flow for each variant instead of one flow with sections. | | | - If two tasks have identical steps, make them one flow. | | | 4. Write each flow file | | | - Put each flow in its own file in a flows/ subfolder, named flows/