Answers
My agent is split into profiles by area and channel, and each knows something different. How do I fix that?
Decide first what should be shared. Splitting an agent into profiles is a sound way to keep areas apart, and the trouble starts only when a decision made in one profile also has to bind another. What belongs to one profile alone, such as its voice, its tools and its notes about its area, stays there. What every profile must follow, such as a price, a customer rule or a call about how a task is done, belongs in one place outside all of them, recorded once and read by each profile before it acts. Arroway is that place: a project your assistants connect to, where a decision is recorded once, a person approves it and every connected assistant reads it. Any assistant that can connect to an MCP server can read it. Arroway does not merge the profiles' own memories or reconcile what each one already believes; it holds what you decide to share. Use it when the same decision has to hold across areas. The install page is the first step.
Last updated October 31, 2026
Why one agent turns into several that disagree
Splitting by area or channel solves a real problem: a finance profile does not carry the marketing thread, and a support channel has its own tone. The cost is that each profile builds its own picture of the team. The same fact lands in one of them and not in the others, and a correction given in one channel reaches only that channel. After a few weeks it stops feeling like one assistant: the same question asked in two places gets two answers, each reasonable from what that profile knows, and you become the one who carries decisions between them. No profile is malfunctioning. The memory is split along the same lines as the agent.
Which things belong to a profile, and which to the team
A short test sorts it. If a line would be wrong in another profile, it is the profile's own: the vocabulary of an area, the checklist of one routine, the tone of one channel. If it would be wrong to hear it contradicted in another profile, it is a decision of the team: what a refund costs, which customers are left out of a campaign, that a task needs a person's approval before it ships. The first kind stays where it is. The second kind is written once, with who decided it and when it ends, and every profile reads it. Keeping the two apart also prevents the opposite failure, a shared memory so full of one profile's detail that every agent carries what only one needs.
When to use Arroway
Use Arroway for the second kind: decisions that must hold in every area and every channel. You or an assistant records the decision on the project, and it stays a proposal until a person approves it; it shows who approved it and the condition that ends it, and a newer decision names the one it replaces. Each connected assistant reads the project when it starts a task. Separate projects keep separate circles apart, so material from one area or client does not reach another unless you put it in the project they share. Arroway does not read or merge what each profile already remembers, and it does not decide for you what is shared. The first step is the install page.
What it looks like in practice
Someone runs four agent profiles: sales, support, finance and a general one on messaging channels. Sales tells a customer that a pilot is free for 30 days. Support, which never learned that, tells another customer that a pilot starts on the paid plan. The finance profile has the right number and nobody asked it. Each answer is consistent with what that profile knew. The owner decides that pilots are free for 30 days, records it on the project and approves it. From then on the four profiles read it when they start a task. When the owner later changes it to 14 days, the new decision names the one it replaces, and all four read the new one. Nothing here was measured; the person and the profiles are illustrative.
Questions people ask about this
- Should I go back to a single agent instead of profiles?
- That is a design choice this page does not make for you. Profiles keep areas and tone apart, which is useful. The page is about the decisions that must hold across them: write those once, outside the profiles.
- Does Arroway merge the memories my profiles already have?
- No. It does not read or merge what a profile has stored. It holds what is recorded on the project, and each profile that connects reads that.
- How do I try Arroway?
- Install it in the tool you already use — the install page has one route for Claude, ChatGPT, Codex, Cursor or any MCP tool — and sign in when the tool asks. From then on, sessions open by reading the project and close by recording what was decided.
Where this is verifiable
Product documentation on this site (How it works, Install) and the sanction, supersession and expiry-condition rules in the sanctioned product spec, read on 31 October 2026. The question comes from public posts by people who run several agent profiles and bots; no tool's own documentation is described here, and no profile feature of any program was measured. Everything described here about Arroway is behaviour the tools apply today, not roadmap. The person and the profiles in the example are illustrative.
https://www.arroway.app/en/answers/one-agent-many-profiles-each-knowing-something-different