Answers
How to install and use Arroway in the main AI ecosystems
You choose the ecosystem you already work in, connect the Arroway server there, and start working — the installation page shows one route at a time instead of a list of every possibility, and it never asks you to sign in before the moment a sign-in is actually needed.
One route at a time, per ecosystem
The installation page begins with a single question — where do you use AI? — and reveals only the applicable path. Claude, ChatGPT or Codex, and other MCP tools each get their own route, with the commands shown on demand rather than up front. There is no generic "IDE" instruction, because the interfaces are not the same.
The plugin is offered only where it is supported
The connection to the server is what makes the memory readable, and it is the universal part. The plugin adds the local skill and the local notices, and it is offered only on the surfaces where the client confirms support — never presented as a requirement.
Personal account and team workspace, side by side
Both paths are shown without asking what kind of account you have: a personal account gets a private address, and a Claude Team or Enterprise workspace gets the OAuth address of this site, with each person authorizing individually. That is what keeps each person's authorship their own.
What it looks like in practice
You pick your tool, connect, open a new conversation, and ask the assistant to read the project before starting. If the project is empty, you point it at the documents and rules that already govern your work, and it proposes what to record.
Questions people ask about this
- Where do I actually do it?
- On the installation page of this site, which is the only place that describes the routes and the steps. This page answers what installing means; it does not keep a second copy of the instructions.
- Do I need to know what MCP is?
- No. The routes are written for the interface you see in your tool, not for the protocol underneath.
- Is there anything to keep updated on my machine?
- No. What gets installed carries only the trigger and the transport, and it is frozen at install time on purpose — everything that could change lives on the server, so an update reaches everyone at once.
Where this is verifiable
The installation page and the distribution decision recorded in the repository. Availability in a given directory or marketplace is stated only after external confirmation.