Connect your agent to Nexus

Connect Dot, Codex or another compatible agent, choose vault access, and use shared skills and project memory.

Use a connected agent such as Dot to work with the Nexus documents and boards you authorize. The built-in Nexus agent is separate and does not require installing an external integration.

1. Connect in your agent app

If your app offers Ionia Nexus Cloud in its integrations or plugin catalog, select it and choose its connect action. Availability and button names vary between apps.

If your app supports custom remote MCP servers with OAuth, add a server named Nexus with this address:

https://nexus.ionia.sh/mcp

Choose OAuth sign-in. Never paste your Nexus password or a token into chat. An app that supports neither the integration nor remote MCP with OAuth cannot use this connection flow yet.

You can always open the Nexus connection walkthrough for setup and skill downloads.

2. Review vault access

The agent app opens Nexus sign-in. Select the intended vault and saved connection, or create your own access if you are an owner or editor. Your connection stays within your vault permissions. Choose the folders or documents and permitted actions. Use Add another vault if needed, then review and approve.

You can prepare access in Nexus’s Agent connections settings first. Saving those settings alone does not finish connecting the app; the OAuth approval flow begins in your agent app. No skill file grants permission to read or change a vault.

3. Make a first request

Ask your agent:

List my available Nexus vaults, then show the boards in the vault I choose.

Choose the intended vault when asked. Check Activity in Nexus’s connection settings for recent tool use. Missing boards may indicate limited scope or an empty vault, rather than an expired sign-in.

Then try a concrete request, such as:

In the Acme project board, create a ticket to improve the welcome page. Include the problem, expected behavior, acceptance criteria, and links to relevant project context.

The agent needs permission to create tasks and read the relevant context. Review its result and the returned Nexus link.

Workflow skills through the connection

Nexus advertises its workflow skills through the connection. Compatible agents can read them using skill.read, without downloading or attaching files. Nexus recommends loading the board skill before card changes and the delivery skill for ticket implementation and PR handoff.

• Nexus Task Board: create and update cards while preserving their original documents.
• Nexus Ticket Delivery: gather context, enrich a ticket, implement and validate the work, then link the pull request and update status based on evidence.

Your agent app decides when to load the guidance. If it caches tools, refresh its tool list or start a new chat. You can ask: “Read the Nexus Task Board skill through the connection before updating this board.” This does not require granting access again.

Offline or manual fallback

Downloads remain available from the Nexus skills page. For an app that imports skills, place each download in a folder named nexus-task-board or nexus-deliver-ticket, respectively, and rename the downloaded file SKILL.md. Import that folder through your agent app’s supported skill workflow. If Dot or another app accepts instruction files instead, attach the file and ask it to follow those instructions for the task. Skill installation support varies by app; Nexus does not automatically install files into another app.

Nexus Desktop versions with Export skills… in Agent connections include offline copies of both folders. Choose a destination to export them without overwriting an existing customized copy. The online downloads provide the current published versions.

Skills do not expand permissions, replace the built-in hosted agent, or schedule work. A task due date alone does not create a reminder or recurring run.

Shared project memory

Shared memory lets Dot, Codex and the built-in Nexus agent reuse a project’s decisions, lessons and procedures across chats. Memories are ordinary Markdown records under that project’s memories/ folder, with a summary, source reference and history. They supplement the board and project documents; current requirements and task status remain authoritative.

Find and save context

Ask a connected agent:

In Ionia, find the shared memories for projects/nexus and read the ones relevant to this ticket. Check the current board and source documents before acting.

To save something deliberately:

Save this as a shared project decision for projects/nexus: [decision and reason]. Cite [source document or discussion].

The connection exposes memory.list, memory.read and memory.create. Agents must follow pagination even when a page is empty. Reading uses existing document permissions; saving also requires Create documents. That permission permits ordinary document creation within the approved scope, not only memories. Ask the vault owner to approve it if it is missing; do not reconnect all your vaults.

Use the built-in agent

The built-in agent receives bounded, permitted memories for the project alongside the current page or selected boards. After a completed project chat, choose Save project memory…, review the type, summary and source, then select Save shared memory. The saved receipt persists when you reopen the chat. Only the reviewed memory is shared; the rest of the private conversation is not copied automatically.

Correct or retire a memory

Open the memory’s document properties to edit its summary or source. A connected agent with field-update permission can use document.fields and record.fields.update with the current revisions. Mark an outdated memory superseded to remove it from current discovery while retaining its history, or archive the document through Nexus.

Memories are shared with people and agents that can read their project folder. They are not personal chat memory, instructions that override your request, or permission grants. Source links do not automatically fetch content or expand access.

If your app does not show the memory tools yet, use its integration Refresh action to update the tool catalog. Existing authorized sessions can keep working without disconnecting and reconnecting. Client support for automatic discovery varies; asking the agent explicitly is the most reliable starting point.

Add another vault without reconnecting everything

As a vault owner, open Vault setup → Connected agents, select your existing connection, choose the new vault’s access, and select Add vault access. Existing vault grants remain unchanged. Ask the agent to list its available vaults again.

Manage or revoke access in Nexus. Until-revoked connections renew automatically while retaining membership and permission checks. An explicitly chosen expiry or revocation still applies. If a request fails, inspect the error and connection scope before repeatedly reconnecting all your vaults.

See Set up a Nexus vault for invitations and Nexus quick start for the full context-to-ticket workflow.

Your vault’s shared skills

Create reusable instructions in Agents → Skills, then choose whether they are enabled and available to connected agents. See Shared agent skills for the controls and permission boundaries.