Galaris

Build your agent team

Build a small team with clear roles, model profiles and authorised tools. Add a specialist when the work needs distinct capabilities.

An assistant to help you get started

The first administrator is offered the Galaris assistant with the internal engine, current profile and access to product documentation. Ask how to organise your team or configure a feature: it can look up sources and guide you. Its identity, role, models and permissions remain customisable; synchronisation preserves your choices and its deletion.

An agent can have just a first name; a last name is optional. Its stable code identifies it in integrations and its workspace.

An agent has a lasting role

Identity combines a job, instructions, model profile, Task harness, skills and tool connections. You can inspect and adjust this setup between missions. The Task harness is separate from the conversation controller.

Specialise for a reason

A research agent may collect sources while a writing agent prepares a note. A technical agent can use a console. Different roles are useful when skills, environment or access genuinely differ; the parent task keeps contributions connected.

Assign the access the role needs

Activate relevant connections and functions. Check effective capabilities rather than assuming that an installed Tool is available to every agent. A skill supplies a method, not additional access rights.

Malik’s team — Ariane, Louis, Nora and Sacha: coordination, budget, logistics and communications in Horizon Workshop.
Malik’s team — Ariane, Louis, Nora and Sacha: coordination, budget, logistics and communications in Horizon Workshop.C09
Ariane’s identity — Manager, identity and role of the event-coordination agent.
Ariane’s identity — Manager, identity and role of the event-coordination agent.C10
An agent’s models — Configurable model resources in Ariane’s settings.
An agent’s models — Configurable model resources in Ariane’s settings.C11

Before adding another agent

Identify the distinct contribution, the required access and how its result will return to the requester. Start with a small team that can complete a clear task, then expand when the work justifies it.

A stable identity in a changing team

The profile specifies a permanent code, name, avatar, personality, job and human manager. An agent can belong to several teams of people and agents. Selectors show permitted contacts or manageable agents for the requested action.

Team membership authorises certain conversations; it does not automatically share every document. Read and write access belong to the resource. The agent profile also shows harness state, logs and tasks blocking an environment change.

The code stays stable throughout the agent’s lifetime. After deletion, it can be reused for a new agent without erasing the previous history; a code belonging to an active agent is rejected.

Share a document with the team

Ask your assistant to prepare the team

“Create a research agent and give it only the reads it needs”: with authorised AgentAdmin access, an agent can create or edit specialists, manage their teams and connections, adjust local permissions and choose a compatible harness. The 34 functions recheck the human manager’s current rights and agent scope on every call.

Only humans grant administrative connections. An agent cannot delete itself, change its own manager or assign itself these privileges. The Galaris assistant receives them on creation; customisations and revocations are preserved.

Upload a portrait, read it from an authorised resource or request generation with a configured image model. YOLO mode is off by default and approves new requests after explicit confirmation; function blocks and resource access rights still apply. Choose approvals and permissions.