Nexus quick start
Turn shared context into a clear ticket, agent-assisted work, and a reviewed result.
Nexus keeps the context, task, and result together. Start with the vault that should own the work, then follow this loop.
1. Add context to the vault
Create or open a project folder. Add its purpose, requirements, constraints, and supporting documents. Use the folder overview for context that applies to the whole project. Check that changes have synced before asking someone on another device to use them.
2. Create a ticket and enrich it
Create a card on the project’s board. Give it a clear title and describe the outcome, acceptance criteria, and links to relevant context. Assign a vault member and add tags or a due date when useful.
For example: Add a password-reset link to sign-in. Describe where the link belongs, what a successful reset looks like, and which errors need handling. Link the design and repository rather than making the agent guess.
3. Use your agent to build it
Give your connected agent the ticket link and a concrete request:
Read this ticket and its linked context. Implement the change, run the relevant checks, and report the result. Ask before expanding access or making destructive changes.
A coding agent also needs access to the repository and development tools. Nexus access alone does not grant repository access or make the built-in page assistant a coding environment. Use the built-in agent for supported vault work, or your connected coding agent for implementation.
Keep the agent’s vault scope appropriate to the project. The built-in hosted agent is managed for your workspace; you can use it from your own device when it shows online. Review proposed document changes before applying them when Nexus presents an approval step.
4. Link the result and update the status
Ask the agent to add the pull request or other deliverable to the ticket, summarize what changed and which checks passed, and update the board status. Use Review when human review remains; move to Done only after the acceptance criteria are met.
Add the pull request link and test results to this ticket, then move it to Review. List anything that still needs my attention.
Open the ticket to confirm the link and status were actually saved. A chat reply alone is not evidence that the board changed. Agents can only update the ticket when their connection permits task changes.
More help
-
Set up a Nexus vault: create a vault, connect your agent, and invite your team.