After setup — usage
How to use AiAkiv
See how AiAkiv differs from plain search — poke it below, no signup. Like it? Connecting takes a minute; then let your AI drive it (below) or walk the eleven steps yourself.
To ask the sample project's real build history with your AI, head to the demo (/tour-demo).
Learn by letting your AI do it
Give the AI you just connected the sentence below. It runs the real tools one step at a time, explains each result, then moves on. Stop whenever you like. (On ChatGPT — a new chat starts with the connector OFF. Click + in the composer and pick AiAkiv, or start from “Try in chat” on the connector's page.)
Use AiAkiv's mweft_guide(topic="tour") to fetch the usage tour and TEACH it to me. One step at a time only — explain what and why first, then wait for my reply before the next step.
Eleven steps
See where your saves go
Say →ak where do my saves go?Tells you the team / project / domain your saves land in. Switching is done in the console. It's shown on every save and search, so it's always visible. If the project has a persona (a role instruction), the AI answers in that role — set or change it on the project card in the console.
List your projects — and switch where saves go
Say →ak list my projectsYour AI calls mweft_list_projects and shows every project you can reach, each with its own switch link (switch_url). The one marked “(Main)” is where saves go right now. To change it, take the link for the project you want and click it yourself — that click IS the switch (and the confirmation). No AI or tool can change Main on its own; only you can, via that link (or the console).
Save your first memory
Say →ak save thisSave anything. Nothing to save yet? Say “ak save ‘AiAkiv connected’” to leave a first memory. AiAkiv is not the right place for source data. Keep original documents in your team's own repository or on GitHub, and save in AiAkiv the conversations with your AI that led to those documents. Save only the important summaries here.
Get tag suggestions
Say →ak suggest tags tooWhen it saves, the AI proposes 2–4 fitting tags. For the ‘connected’ memory, have it propose an ‘aiakiv’ tag. Tags make a memory reliably findable later.
Attach the tag to that memory
Say →ak tag that memory ‘aiakiv’Adds the tag you want to the memory you just saved — without re-saving it.
Find it again
Say →ak search ‘AiAkiv connection’Search for what you saved and pull it back. If the summary is too thin, the AI fetches the full original text.
Five ways to search
Say →ak search … · ak @team · ak @userFive ways to search. ① by meaning “ak search …” ② by keyword “ak find things about ‘AiAkiv’” ③ by tag “ak find the ‘aiakiv’ tag” ④ from a team “ak @TeamName …” or a team part “ak @PartName …” ⑤ from one person “ak @you@email.com …”, or “ak @you …” if an alias is set @ search tags are assigned automatically by the system. @you@email.com is the email you signed up with. In each team you can appear as an alias instead (Console → Teams → Manage).
Save continued content
Say →ak keep saving thisLong notes or multiple pieces are saved in order, one after another. Even very long content is split and chained — never truncated.
(Later) analyze communities
Say →ak group my memories by themeOnce a lot is saved, see the themes AiAkiv found. Only when you want it — meaningless on an empty account.
Tidy up the demo memory
Say →ak hide that test memoryDeprecate (hide) the test memory this tour saved. It is NOT deletion — the data stays; it just stops appearing in search and recall. Keep it if you like.
Good habits to keep
Say →ak save · ak searchSave only when you say ‘ak’. Ask it to search before answering from memory. Use one name per real thing (so recall weaves). Fix a wrong tag or a mis-saved memory with “ak fix / hide it”. Change where saves go in the console.
Now open the console to create teams / projects and get going.
Open console →Machine-readable version for AIs: /llms-tour.txt