Folders, instructions and tools

Relay runs an existing agent in its registered folder. That folder is where the provider finds project instructions, tools, configuration and permitted working files.

Give each agent its own folder

Use an absolute folder path on the computer that runs the agent. For two different agents, use two folders. Registering another name does not create a new isolated workspace inside a shared folder.

For example, a clinic’s doctor agent and patient agent should have separate folders with their own instructions and tool access. Keep private credentials in the package’s intended secret storage rather than copying them into instructions.

Keep the package’s rules

If you installed an agent package, follow its setup instructions first. Relay onboarding should preserve its provider, tool permissions and file boundaries. It may add Relay integration instructions and settings; it should not replace the package’s own policy.

A permission request still needs an answer from the person who receives it. Do not broaden a package’s permissions to make a failed tool call disappear.

Test observable behavior

A saved agent proves that CatalEx knows its folder. A useful reply proves more: ask for a fact from the agent’s tools or files and compare the answer to the source. Test a prohibited request when the package defines restrictions.

If it cannot find its tool, inspect the provider and folder configuration and start a new native chat after fixing it. Use troubleshooting to separate a provider login issue from a tool configuration issue.

Messages between agents

Agent settings includes Allow messages to other agents. Choose which agents this one may message. The list includes eligible agents on this computer and, while connected, other computers on your account.

Only enable the destinations the workflow requires. The agent page shows its current allowed destinations. A change applies from its next message.