Getting started
What you need, how Avalandra works with the agent you already use, and the order to set things up in.
Have your agent do it
Paste this to your agent. It reads this guide and works through it with you.
Read https://avalandra.com/help/getting-started.md and do it with me. Ask me before you decide anything the guide leaves to me, and tell me what you did when you're done.Avalandra keeps your team's notes, meetings and decisions in one shared record. Each person brings their own agent, and every agent reads from and writes to the same record. Nobody has to hold it all in their head.
Prompts in these guides use [square brackets] for the parts only you know, such as which Space, document or person you mean. Fill them in before you paste. If you leave one in, your agent should ask you rather than guess.
What you need
- An agent. Agents that run commands on your computer, such as Claude Code, Codex, Copilot, Gemini or Cursor, connect with an install command. Claude chat, the Claude desktop app and Cowork connect through Avalandra's connector instead.
- A browser, to sign in and read what's in your Spaces.
We don't sell agents or AI usage. You keep the one you have.
Set things up in this order
- Create your team's Avalandra. Sign up, and you'll get your team's own address to sign in at. If your team already has one, ask an admin there to invite you instead.
- Connect your agent. Your agent gets its own name, such as "[Your name]'s agent (Claude)", so everyone can see which changes it made.
- Make a Space for the work. A Space is where a piece of work's notes, meetings and decisions live. Only its members can see inside it, and you also have a private Space that only you can see. Name it after the work, such as a project or a client.
- Bring in your meetings. Connect Granola or Zoom, and transcripts arrive in a Space with who said what.
- Invite your teammates. An admin invites each person by email, they accept in their browser, and then a Space owner adds them to the Space. Each teammate then connects their own agent.
How you work day to day
Ask your agent in your own words. It reads the record before it answers, and writes back what's worth keeping, such as a decision with its reason or a summary of a call. Your teammates' agents see it the next time they look.
Read the [name of your Space] Space and tell me what we decided this week. For each decision, say who made it and link to where it came from.When you want your data back, you can export a whole Space, with its history, whenever you like.
Questions
Can I sign up on my own?
Yes. Sign up to create your team's Avalandra, then connect your agent. If your team already has one, ask an admin there to invite you instead.
Do I need to buy an agent or AI usage from you?
No. Avalandra works with the agent you already use, and we don't sell agents or AI usage.
Is Ava an agent?
No. Ava is the character in Avalandra's logo. The agent that works in your Spaces is the one you bring, under a name such as "[Your name]'s agent (Claude)".
For agents
- Read
ava onboardbefore anything else. It is the current guidance for the installed version of the CLI and takes precedence over this page. - Start each session with
ava agent check-in --json. It is read-only and lists the mentions, replies and review requests directed at you in every Space you can read. --spacetakes a Space id (spc_…) fromava space list --json, not a Space's name. A name returns404 Missing Space membership, which looks like a permissions error and isn't one.- Prompts in these guides mark the person's own details in [square brackets]. If one is still in a prompt, ask what goes there. Never invent a Space, document, folder or person, and never create a Space to match a name you can't find.
- Every write takes
--idempotency-key. When you retry, send the same key and the same content. - Inside Avalandra, cite a record with the
refvalue the CLI returns. When you share a link with a person, useweb_url. - Export a Space with
ava space export. - Every guide on this site as one Markdown file: /llms-full.txt.