Change your assistant, keep the file

Anyone who has worked with an AI assistant for a few weeks knows the moment. A conversation has grown long and useful, the assistant knows the client, the preferences and the open points, and then the chat is lost, or full, or you would like to try a different assistant. The knowledge was in the conversation, and the conversation is gone.

A file belongs to the office#

A well-run office does not keep its knowledge in the head of one employee. It keeps a file. Nabcloud applies the same idea to assistants. Notes, decisions, projects and documents are stored in the workspace. When an assistant learns something worth keeping, it is written there, with the project it belongs to, and the assistant can later search what has been learned, confirm it, or mark it as no longer true.

A new chat then begins with a short instruction, for example: read the project and tell me where we are. The assistant reads the file and continues.

What follows from that#

You can change assistant. Connect a different one, such as Claude, ChatGPT, Gemini, Grok or any assistant that supports MCP, and it reads the same file. Nothing needs to be re-explained or migrated.

You can use several. Each connected assistant appears as its own agent with its own role and permissions, and all of them read and write the same records.

You are not tied to our choice. Nabcloud has no AI of its own. We do not choose the assistant for you and we do not bill you for one. You keep paying for yours where you already do.

You can leave. Memory, projects and files can be exported at any time. A record that cannot be taken away is not really yours.

An illustration#

The office and the people here are made up.

A three-person accounting office has worked for a month with one assistant on its quarterly VAT preparations. The notes record which clients file monthly, which deadlines were agreed, and that one client prefers calls to email. In the autumn the office decides to try another assistant for the same work. The partner connects it, gives it the same role and permissions, and starts with: read the project and tell me where we are. The summary it gives matches what the office knows.

An honest limit#

Keeping the file tidy#

• Record decisions, not conversation. A decision with a date and a reason is useful in a year.
• Correct what is no longer true rather than adding a second note beside it.
• Keep client matters in their own projects, so an assistant reads only what is relevant.

You will find the technical description in memory and your data, and a summary under one memory and your AIs.