# Manage learning behavior Source: https://www.hyperagent.com/docs/learning/manage-learning-behavior > For AI agents: the documentation index is at https://www.hyperagent.com/llms.txt and the complete documentation in one file at https://www.hyperagent.com/llms-full.txt. Any docs page is also served as Markdown by appending `.md` to its URL. Decide how much your agent can change on its own: propose and wait for you, save without asking, or nothing at all. Your agent picks things up as it works. You decide what happens next: it waits for your approval, saves on its own, or lets it go. Let an agent save small facts on its own while changes to its instructions still wait for you. Mixed setups are the normal ones, and no level moves unless you move it. ## Set how much it learns [#set-how-much-it-learns] Open your agent and go to its **Knowledge** tab. The **Self-learning** section holds one row per kind of change, and each row takes a level. * **Suggested** proposes and waits. New agents start here. * **Auto-saved** skips the approval step, so small, obvious lessons land on their own. * **Off** keeps that type out of the agent's hands. You can still ask for one directly. Raise a type to Auto-saved once the agent has proven itself there. Nothing changes the level but you. ### Which level to use [#which-level-to-use] * **An agent you use yourself, every day.** Memories on Auto-saved. It picks up your standing preferences as it works, and you keep reviewing the changes that reach further. * **An agent your team runs.** Leave everything at Suggested. Its lessons land in the team's knowledge, so one review keeps the shared brain clean for everyone. * **An agent in a channel you don't control.** Curated, the knowledge profile that turns learning off and narrows what it reads. Hyperagent applies it for you the first time an agent joins a Slack channel. ## What it can change [#what-it-can-change] A fact or preference worth keeping: a threshold you set, how you like a report opened. A method worth repeating. On a team agent, the skill belongs to the team, so this one always waits for you. An addition to the agent's instructions, appended below what you wrote. The agent editing its own setup: instructions, tools, skills, model, schedules. Agent configurations is the one row without a Suggested option. A configuration change happens while the agent works, so it arrives as a card in the conversation. Auto-saved tells it not to wait for your click. ## Let a Slack channel teach it [#let-a-slack-channel-teach-it] By default only you teach your agent. On the same **Knowledge** tab, just below **Thread search**, turn on **Learn from others in Slack** and the channel's members do too. Worth doing when you trust the room. Even then, nothing from a channel auto-saves, so no one's message becomes standing knowledge without your review. ## What never saves without you [#what-never-saves-without-you] Three things stay in your hands whatever the levels say: * **Anything the team shares.** A skill on a team agent, or a configuration change saved into a team's workspace. A shared skill's instructions, scripts, and credentials affect every member at once. * **Anything from outside.** Runs that arrive through Slack, email, or a webhook. * **Anything that widens the agent's reach.** Keeping a browser session signed in, or letting a schedule write to your connected apps. Everything held for review waits in one queue. See [Manage suggestions](https://www.hyperagent.com/docs/learning/manage-suggestions). ## Undo anything [#undo-anything] Open any memory or skill and **Version History** sits at the bottom of its detail page. Each entry says whether you or the agent made the change. Restoring is itself reversible: your current version is saved to the history first. Instructions are safer still, since the agent appends below what you wrote and never over it. ## FAQs [#faqs] Turn **Learns automatically** off on the agent's Knowledge tab, or pick the **Curated** knowledge profile, which also narrows what the agent reads. A prompt suggestion only adds to the instructions, and it comes after a conversation, from an analysis of how the work went. A configuration change happens during a run, when the agent is working on its own setup, and instructions are one of several things it can touch there. Yes. A thread's **Learning** popover narrows what that conversation may propose, and runs the analysis on demand instead of waiting. It changes that thread only. A conversation can also propose a **rubric**, which agent settings don't cover; see [Rubrics and evaluations](https://www.hyperagent.com/docs/learning/rubrics-and-evaluations). No. A memory can belong to one agent, but every skill belongs to a workspace, yours or a team's. That's why skill learning on a team agent is always a shared change. Less than it sounds. It applies only to the types you raise, wide changes wait for review anyway, and everything saved can be restored. The real risk is accumulation, so look over what the agent has kept now and then.