01
Coordinate agent work
Keep tickets, sessions and handbacks in one workspace. NautBot coordinates parallel assignments; you review the result.
← All products
Agentic development / Team workflowsEarly stage
xNaut
Your agents are coding. What's ready to ship?
A development dashboard for tickets, parallel agents, isolated worktrees and verified handbacks. NautBot coordinates the work; your team reviews the result.
The reason
I wanted fewer windows and a complete development workflow.
xNaut began as my own CLI for snippets and DevOps work. As coding agents became part of my routine, I wanted terminals, project files and agent sessions together.
The workspace now connects tickets to implementation, separate verification and human review. Worktrees and supported sandboxes keep tasks apart while I follow the work.
Inside xNaut
What you can do.
Select an image to take a closer look.
02
Develop an idea with NautFlow
Work through questions, requirements, architecture and implementation. Guided stages make the decisions explicit before agents build.
03
Separate the work
Git worktrees give tasks separate working directories. Supported sandboxes such as exe.dev provide remote build and test environments.
04
Review the evidence
A separate agent checks the implementation and returns test evidence. Optional signing can cover recorded workflow steps; people decide when work is finished.
Follow the xNaut workflow
XNAUT / FROM TASK TO REVIEW
Many tickets run in parallel. Follow ticket #042 through its full cycle.
01
Ticket
Create a ticket with a task description in xNaut, or pull it from GitHub. Multiple tickets and agents can run in parallel.
Every step can optionally be signed with Securosys. Shown here as an illustration.
Availability, scope and technical resources
The Enterprise version uses its own registry to connect xNaut clients for team collaboration. The offer is to establish a working development process with your team: ticket intake, execution environments, model connections, verification and human approval.
The open-source version is for individual use and does not include the Enterprise teamwork model. xNaut is an early-stage development tool; deployment scope and supported integrations are agreed before adoption.
Optional Securosys signing can be attached to workflow steps. A persistent Zellij session does not itself recover every failed agent process. Final review and ticket closure remain human decisions.
Technical questions
How do the individual and team editions differ?
The open-source edition is for individual use. The Enterprise version uses its own registry to connect xNaut clients for a shared development workflow.
What is NAUT-Flow?
An end-to-end flow for building a product, from idea and business case through requirements, implementation, testing and release. Guided mode leads you through a questionnaire. In expert mode, you define everything yourself.
Who is xNAUT for?
Individual developers can use the open-source edition for their own agents and tickets. Development teams use Enterprise to connect their xNaut clients through its registry. xNaut is in an early stage of development.
Which platforms are supported?
macOS is the primary platform. Early Windows installers are available; some workflows remain macOS-first. Check xnaut.dev for current requirements.
Do we need a cloud account?
For individual use, local models or your own cloud-model credentials can be used. Enterprise teamwork connects clients through a separate registry. The team configuration is set up separately.
What does signed evidence prove?
With Securosys configured, checkpoints over captured execution records are signed. Exported bundles can be checked offline for signatures, hash chains and Merkle roots using a separately trusted public key. This proves integrity of the signed record, not work quality or completeness of activity outside capture.
xNaut guides