# Autowiki

Source: https://www.hyperagent.com/docs/knowledge/autowiki

> 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.

Keep customer history, project decisions and operating rules in pages your agents can use in later work.

A repeat customer question can depend on several earlier conversations. You need the problem, the agreement and any action still outstanding. **Autowiki** brings eligible knowledge into linked pages that people can inspect and agents can consult in later work.

**Dreaming** is the background process that maintains those pages. It reads eligible threads, saved memories and documents in the workspace, then creates or updates the wiki. A page can hold a customer's current terms, the decision behind a project change, or the rules for a recurring process.

Autowiki preserves useful context beyond the conversation where it arose. Your agent can consult that reference instead of reconstructing the history each time.

Autowiki is in beta. To start a wiki and check its first pages, follow [Set up and use Autowiki](https://www.hyperagent.com/docs/guides/set-up-autowiki).

## What a wiki page keeps [#what-a-wiki-page-keeps]

A page brings related knowledge together, rather than saving each sentence as a separate note. It has a title, summary, linked pages, sources and version history. Pages can describe people, customers, products, projects, systems, processes and policies.

The distinction from other [knowledge](https://www.hyperagent.com/docs/knowledge) is the job each kind does:

Memories keep standing facts, preferences and corrections. They can contribute to a wiki page and remain useful as separate records.

Documents hold source material or authored work, such as a care guide or proposal. A wiki can cite them without replacing them.

Skills describe how to do a job. A wiki page can explain a business process, while a skill gives the agent a method to follow.

Threads keep the conversation and work for a request. Autowiki draws useful knowledge from eligible work into a reference for later requests.

Example

The Juniper Café page brings together its standing order, the agreed remedy for a complaint, the settled status and a root-check procedure for future orders. An agent preparing for the next customer conversation can begin from that history.







## Sources [#sources]

Dreaming works within the selected workspace. It draws from the work and reference material you keep there:

Eligible threads contribute the conversations, decisions and findings from your work with agents.

Saved memories contribute lasting facts, preferences and corrections within the relevant workspace or agent's knowledge.

Documents contribute reference material and revisions, such as a policy, project brief or customer guide.

An agent's learning settings and where the material belongs affect what contributes. A customer page can bring an agreed term from a thread together with a saved preference and a reference document.



## How pages stay current [#how-pages-stay-current]

The first build starts with saved memories, then processes the recent activity window you choose. Daily dreaming reviews later activity and updates the pages, so the reference develops as the work continues.

Background maintenance reviews recent activity daily. Owners and Editors can also request an incremental dream to catch up on activity.

Requested corrections save without waiting for the next dream. Owners and Editors can edit a page or ask an agent to update it.

History shows which pages each dream created or updated. If you pause daily dreaming, the pages remain available for you and your agents to use.



## Who can use the knowledge [#who-can-use-the-knowledge]

There are two choices to make: where the knowledge belongs, and who should be able to maintain it. Your agents also have their own knowledge settings, so you can give each one the context its work needs.

Personal keeps your wiki separate from the team's. You manage it yourself, and your agents use the pages their knowledge settings allow.

Workspace members can read shared pages and browse pages kept for its agents. Use this home for customer history, policies and decisions the team needs together.

### What your workspace role lets you do [#what-your-workspace-role-lets-you-do]

In Personal, you have owner access. In a shared workspace, the same Owner, Editor and Member roles you use elsewhere in Hyperagent apply to Autowiki.

Members read the wiki and use workspace agents. They do not edit its pages or change daily dreaming.

Editors correct pages and can archive or restore them. They can request a dream while daily dreaming is on.

Owners maintain pages and manage the workspace's members. They also turn daily dreaming on or off.

The same roles apply when an agent makes a page change for you. Members can use an agent's answer. Owners and Editors can also correct the wiki pages it uses.



### Workspace roles [#workspace-roles]

Use this action lookup for shared work. In Personal, you have owner access.

| Action                              | Owner | Editor | Member |
| ----------------------------------- | :---: | :----: | :----: |
| Read pages and history              |  Yes  |   Yes  |   Yes  |
| Correct, archive and restore pages  |  Yes  |   Yes  |   No   |
| Turn daily dreaming on or off       |  Yes  |   No   |   No   |
| Request a dream or stop active work |  Yes  |   Yes  |   No   |
| Permanently delete one page         |  Yes  |   No   |   No   |
| Wipe the whole wiki                 |  Yes  |   Yes  |   No   |

### What your agents can use [#what-your-agents-can-use]

An agent's knowledge settings are a separate choice from your teammates' roles. An agent can use the pages kept for it and the shared pages its settings allow. Another agent's pages do not automatically become part of its knowledge.

Give agents shared context when several should work from the same customer history or policies. Keep specialist context with the agent when it mainly applies to that role. Check the agent's [knowledge settings](https://www.hyperagent.com/docs/concepts/agents/knowledge-access) when you want it to use more shared context.



For setup, page corrections and daily dreaming controls, use [Set up and use Autowiki](https://www.hyperagent.com/docs/guides/set-up-autowiki).

## Inspect, correct and retire pages [#inspect-correct-and-retire-pages]

Sources and version history let you examine how a page developed. History distinguishes dream-written updates from your team's edits, so you can see what changed and who changed it.





Edit a page when terms change or a summary needs correction. You can also ask an agent to update it on your behalf. Archive a page when it is no longer relevant, then restore it if you need it again. See [Set up and use Autowiki](https://www.hyperagent.com/docs/guides/set-up-autowiki#correct-a-page) for the steps and page-management controls.

Review a [customer or project page you know](https://www.hyperagent.com/docs/guides/set-up-autowiki#review-a-page-and-its-sources), then ask your agent a fresh question that needs that history. Ask it to identify the page it used so you can check the answer.

## FAQs [#faqs]

Dreaming builds and maintains wiki pages from eligible work. Owners and Editors can correct the pages directly or ask an agent to make those changes.

Daily dreaming adds eligible activity each day. Check History to see how far it has reached. A correction you save directly does not wait for the next dream.

Your agent can read wiki pages in a fresh thread. Start in the right workspace and ask it to open the relevant page. Its knowledge settings determine which pages it can use.

If you turn daily dreaming off, the pages remain available to you and your agents with the same access. Future daily updates stop until you turn dreaming back on.

The wiki page and the original conversation or document have separate access. Ask the source owner for access when you need to inspect that original material.

Autowiki gives your agent the history, rules and decisions around the work. Through connected integrations, your agent can check current information in your CRM and other systems when a task needs it.