Knowledge
Put manuals and specs in a global library, then enable them per project in chat. The same document can be reused across projects.
Open Knowledge in the sidebar, or from the welcome screen.
Conversion API
PDF and other non-plain-text uploads need a conversion service. .md / .txt files go in as-is.
- Register at MinerU, open API management, and create a token.
- Open Settings → General → Document conversion API.
- Paste the token into API token. Leave API base URL empty for the default.
The token stays on this machine. If it expires, create a new one in MinerU and update the field.
Upload documents
Do not upload a multi-hundred-page manual in one piece: conversion is slow and search is worse. Split by chapter first (for example PDFsam). Use names you can recognize; names must be unique in the library.
- Click Add documents and select one or more files.
- Leave them ungrouped, add them to an existing group, or create a group (handbook name, chip family).
- Conversion continues in the background; you can close the window.
| Status | Meaning |
|---|---|
| Processing | Conversion in progress |
| Ready | Can be enabled and searched |
| Failed | Read the error, delete, and upload again |
You can search, rename, edit descriptions, and move files between groups. Deleting a group keeps the files and marks them ungrouped.
Enable for this project
Imported files do not join chat until you select them:
- Open a project.
- In Knowledge click Select for project, or open Settings → Knowledge.
- Check the documents this project should use, then save.
The composer shows how many documents are enabled. Unchecked files stay in the library for other projects.
When a manual exists, ask AutoC to consult the library before changing configuration.
Import and export
Export one file or a whole group as ZIP, then Import ZIP on another machine. Progress is shown while it runs.