Skip to main content

Agents, skills, and memory

Konnie combines conversations, permitted tools, reusable skills, and memory. These have different purposes: a tool performs an available operation, a skill explains how to approach a recurring task, and a memory retains useful context. None of them creates missing permissions.

An embedded App assistant is Konnie configured for a particular App. External agents and their scoped access are managed through the Agents area; they are not created by adding a Konnie skill. See roles and permissions for access principles.

Teach Konnie in conversation​

Tell Konnie what will help next time: “Keep my updates brief”, “We call these production islands”, or “Start weekly planning with overdue orders.” Say whether the knowledge is just for you or shared with your company. Personal preferences stay personal; shared methods still follow the company's permissions and approval settings.

After a confirmed memory change, the conversation can show a short receipt with the saved statement, audience, and Change or Forget actions. Receipts read the current saved record through your permissions. If it has changed since that conversation, the receipt identifies it as current memory. A suggested method awaiting approval is labeled as a suggestion; it is not yet learned or active.

What Konnie knows​

Open What Konnie knows from Konnie's controls. Search readable statements and methods, filter by personal or company audience, and open an entry for details. Long instructions and internal keys are not required reading.

Correct an inaccurate text memory in place or choose Forget. If someone changes it while you are reviewing it, reload the current version before saving or forgetting. Forgetting stops active use and blocks automatic learning from recreating that same key in the same audience and workspace. You can explicitly teach it again. Earlier conversation text follows its own retention lifecycle. The same fact under another key can still require correction.

Use memories for durable preferences, terminology and context. Konnie selects a bounded amount of relevant context for each task. Live stock, order status and production quantities belong in authoritative records and tool lookups.

Methods and advanced administration​

Skills describe how Konnie approaches recurring work. Their detailed instructions load when needed. The knowledge view shows a short explanation of each applicable personal or company method. System skills supplied with Ennea remain available in administration.

Authorized users can open More options to manage methods, add a memory directly or inspect company research. Method administration shows active and archived methods, search, version history and pending changes. Review the actual Before / After change and open the complete proposed version before approving. Approval applies to that exact proposal; validation or a pending status does not replace the current active method.

When authoring a method, describe its name, when to use it, instructions and reason. Optional category, tags and examples are available in additional details. System skills are read-only; create a company alternative where needed. Archive an obsolete company method to stop loading it while preserving recoverable history. Rollback creates a new version from earlier content and does not reverse operational actions.

A method provides guidance. It cannot grant tools or permissions, replace controlled manufacturing rules, or guarantee that a task succeeded. Load counts describe loading, not successful outcomes. Test changed methods with harmless synthetic or approved read-only scenarios.

Administrators configure organization learning and permitted sources in Control Center → Learning. Personal Konnie settings offer participation for your conversations. Save the setting to change it. Disabling conversation learning prevents that automatic learning path; it does not erase existing memories, conversation history, or explicit memories you separately request.

Dojo Mode asks Konnie to pay extra attention to useful reusable context. It does not override disabled learning, your participation setting, memory permissions, or approval policy. Company research, where configured, is another source of company knowledge; review facts and sources before relying on them.

Shared learning also requires an explicitly activated learning worker under Background work, with a responsible owner, scoped service identity and saved autonomy level. Source access and conversation participation are checked on each read. At Ask before changes and Save drafts, learned memory and skill changes are prepared for review; Full autonomy can activate eligible validated changes within the saved mandate. Learning cannot grant additional permissions or broaden its own sources.

Company research​

Where enabled, More options → Company research in the knowledge view and the company-research panel in the Control Center let authorized users start or repeat company research. Enter the company name, website, optional focus, and private context; add up to five PDF, TXT, or Markdown files of at most 10 MiB each. Select whether to reuse prior documents, read the provider/data disclosure, and explicitly confirm the request before starting. Research has its own provider approval requirements; ordinary chat availability does not establish research readiness.

Research continues in the background. Inspect the run status, report, sources, open questions, and completion time. Download the report as PDF when offered. A completed run publishes reusable company knowledge into ordinary company memories. Review those memories and correct or remove inaccurate entries through the normal memory controls.

The panel retains report history and identifies the active completed run. If a new run fails, previous active knowledge can remain. Cancel ongoing work using the offered control. Deleting a report needs management permission and can be blocked by retention restrictions or legal hold; inspect the result instead of assuming every related piece of data was erased.

Troubleshooting​

If a method is missing, check the current organization and, in administration, its active/archived status. If an edit is unavailable, it may be a system skill or your account lacks management rights. If learned content does not appear, check learning sources, personal participation, pending changes, and validation status. If Konnie repeats an obsolete fact, correct the memory and state the authoritative replacement in the conversation.

See Control Center, chat, and governance.