BackProduct

Saved Agents With Their Own Instructions and Memory

Save project agents with instructions, compatible skills, and memory for reuse in workspace chats and automations inside Aiola.

Panagiotis Visilias

Oct 26, 2026 · 5 min read

Painted desk scene with a laptop and labeled agent cards

A saved agent is a workspace profile you define once and open again later. It stores agent instructions, skills, and memory for chats and automations in that project. You pick the same profile whenever that job comes back.

What does a saved agent contain?

Agents are profiles for chats and automations inside one workspace, and the agents guide documents them. A workspace is one project in Aiola, and these profiles stay on that project. There is no Central Agents page.

Open Agents in the workspace navigation, which is shown by default. The route for that screen inside the workspace is /agents. You can search the list from that same Agents screen.

Filters on that screen narrow the list by source and by category.

Which fields do you set?

The agent editor includes identity, instructions, skills, and memory fields:

FieldPurpose
Name and iconIdentify the agent in pickers
DescriptionSummarize its job
CategoryUse a built-in or custom category
InstructionsMarkdown behavior and operating rules
SkillsAttach provider-compatible skills
MemoryPreserve agent-specific context

Select New agent when you want a new profile. Open an agent when you want to edit its fields. Use the delete action when you want to remove that profile.

How do you write instructions?

The instructions field has two modes, called Write and Preview. Use Write to edit the Markdown instructions. Open the saved agent again when you need to change those instructions.

How do workspace prompts differ?

Workspace prompts are separate from the text stored on an agent. Open them through Workspace Settings, then Workspace, then Instructions, as the custom instructions page describes. Edits are saved to the active workspace’s settings.

These prompts apply to built-in workspace actions. The groups cover dashboard prompts, analysis, and fix or implement actions.

Dashboard quick prompts appear below the composer when a thread has no messages. You can edit prompt text and icons on each one. Remove an entry, or select Add prompt, when the list should change.

Chat on a GitHub issue starts GitHub Issue Analysis. A pull request uses Pull Request Analysis when you choose Chat. Feedback bug reports start Bug Report Analysis from Chat. Feature requests in Feedback start Feature Request Analysis from Chat.

GitHub Issue Analysis also works as a fallback. The fallback applies when an analysis has no dedicated instructions of its own.

Chat on an App Logs entry starts App Logs Analysis. The entry may be an error or a warning. Analyze with AI on Analytics starts Analytics Analysis.

The Fix it action uses different prompts for each record type. GitHub issues use GitHub Issue Fix, while Feedback bugs use Bug Fix. Feedback feature requests use Feature Implementation, and App Logs errors use App Logs Fix. An Analytics indexing issue starts Indexing Fix when you choose Fix with AI. Affected URLs on that indexing issue are added automatically. Fix all for failing pull-request checks starts PR Check Fix.

GUI Lifetime omits the hosted Feedback, App Logs, and Analytics instruction groups. A reduced dashboard default set applies on GUI Lifetime. Prompts that match hosted-only defaults are filtered out.

Hosted Analytics, App Logs, Feedback, hosted MCP, and Setup Health need Pro or the seven-day trial. The trial requires a card and is limited to first-time Pro Monthly customers.

Why does the first skill lock the provider?

The first linked skill locks the agent to that skill's compatible provider. One CLI session cannot load skills from different providers. Remove all selected skills before you switch provider families.

Open a skill to inspect its files and instructions before attaching it. Skills for providers that are not installed are hidden. Search and provider or category filters work across the combined skill catalog. Workspace skill discovery includes .agents/skills and .claude/skills.

User-owned skills can be created, edited, or deleted. Created skills are written to the selected provider’s native directory. Grok bundled skills are read-only; create a separate skill to customize one. Skills you attach are covered on Skills and MCP.

Claude Code, Codex, Cursor, Grok CLI, OpenCode, and Antigravity run in this desktop app. You bring your own subscriptions, and Aiola adds no token markup.

What does agent memory preserve?

The Memory field preserves agent-specific context. Open the agent to edit that field alongside its instructions and linked skills. The profile belongs to one workspace, like the project’s threads and instructions.

Workspace selection also matters when starting a chat from Central Home. Select the target workspace before starting a draft there. That selection scopes files, branches, agents, and record mentions. Existing threads retain their original workspace and execution context.

What should you review on a template?

Templates are starting points you use when you create a new agent. Review the copied fields and the copied instructions before you save. Saving creates the new workspace agent from that reviewed copy.

GUI Lifetime removes templates that depend on Aiola-hosted services. Workspace agents remain available when you use GUI Lifetime. Templates without hosted dependencies remain available.

Where do you reuse the agent?

Pick the agent through the workspace chat composer’s Agent control. Provider and model controls select the local AI runtime and model. Type / to see grouped entries, including agents and skills. Available entries depend on the active workspace and provider capabilities.

Use the same agent for an automation you set up in Automations. Its execution settings include an Agent field for selecting a saved workspace agent. Automations use a fixed workspace, execution configuration, and optional schedule. Run a manual automation from its detail page. That page reports status, duration, output, errors, and linked threads. Automations run only while the Aiola desktop app is open.

Try it in Aiola: download the desktop app, then open Agents inside a workspace. The app runs on macOS 12 or later and on Windows 10 or later. The download is free.

Common questions

More from the blog

Build, ship and fix in one app

Errors, user feedback, GitHub and analytics live next to your coding agents in one desktop app, so every issue becomes a task an agent can take.