Roadmap

What's next, and what's shipped

Directional, not dated. For what changed in each release, see the changelog.

In progress2

  • Add a computer in one command

    Install Nexul on your own computer with one command and it sets up T3 Code, pairs it and keeps it paired, with no Cloudflare or domain needed, so your agents run there. Setup runs every provider side by side, and one you switch off stays out of plays. On Linux, macOS and Windows.

  • T3 Code orchestrator V2

    Keep working when T3 Code moves to its new orchestrator, with no re-pairing, and see the work an agent hands to other agents as a pill on its reply.

Planned5

  • Nexul's own error rate

    Get told when Nexul itself starts failing requests, with the same rule a stack uses.

  • Call notes

    A voice call becomes notes and a summary in the doc, without anyone typing them.

  • Semantic search

    Find docs and tickets by what they mean, not only by the words they share.

  • Runner labels

    Route a job to the runners that carry the right labels, not just the right machine.

  • Automatic TLS

    Let's Encrypt certificates for services served straight from your server.

Shipped57

  • Enterprise edition

    Paste a license key into Settings to unlock enterprise features on one instance, checked offline with nothing sent home. The first two: sign-in through your company's own identity provider, with a switch that turns every other sign-in off, and your own name, logo, accent colour and an imported VS Code theme across the instance. When a key expires the features stop and everything they made stays.

  • External secrets

    Paste a 1Password reference such as op://vault/item/field instead of a secret into a stack's environment, a branch rule, the automation secrets pool, a connector or a sign-in provider. The runner, automations host or server that uses it reads it with its own service account, so a copy of Nexul's database holds no secret, and a changed value shows on the stack with Redeploy beside it.

  • Passkeys

    Add a passkey from your profile and sign in with your fingerprint, face or security key, no GitHub, Google or Discord round trip. Your linked accounts keep working beside it.

  • Workspace calendar

    Plan meetings in a voice channel or at a link, invite members who accept or decline, repeat them, and change or cancel one occurrence or the rest. Everyone gets a reminder in the inbox and on their phone before each one, and a ticket's developer the day before it's due.

  • Times in everyone's zone

    Paste a Discord time code such as <t:1792867165:F> into a message, a thread, a ticket or a doc, and each reader sees it in their own time zone, on the web and the phone, in all nine of Discord's formats; a relative one stays current. Click one to copy its code or download it as a calendar event.

  • A computer with no systemd

    Add a container, or any Linux host that isn't running systemd, as a computer: the install needs no sudo and stays running as a built-in supervisor that runs the Nexul app and T3 Code, starts either one again 5 seconds after it exits, and removes the install when the computer is removed in Nexul.

  • Clone onto a computer

    When a computer has no T3 project for one of a project's repositories, pick Clone beside the T3 project picker and T3 Code clones it next to the computer's other projects, then the picker selects it. Agents do the same with computer_project_create. Create empty project makes a new folder the same way when there is no repository to clone, and setup makes one called nexul-chat, kept as the chat folder, on a computer with no T3 project at all.

  • View as

    Open a person on Team and view Nexul exactly as they see it in a workspace, read only, to check whether their roles give too much or too little. The view ends by itself, with the reason, if their roles change.

  • Projects before code

    Start a project with no repository for a client's docs, or attach a repository that isn't ready to deploy, as plain choices in the wizard, and deploy it later from the project's Services.

  • Invitations that explain themselves

    Each role says what it means in one line, on the invite form and the invite page. The page names no project until the person signs in, then lists the projects their roles open. Expired or deleted links say so plainly, and an existing account is turned away without using up a link meant for someone new.

  • Screens that know your role

    A button you cannot use is hidden, or, for roles with Show locked actions on, shown locked with the reason. Things you could make now have a way back: delete a machine or tunnel once nothing uses it, edit a stack's environment with secrets masked, retry a failed deploy, unlink a branch, archive a workspace.

  • Machine permissions

    Choose who sees each server and who may deploy to, manage or delete it, by role or by person. A new server shows only to the instance owner until they add people.

  • Permissions on roles

    Give people several roles, show each project only to the roles and people in it, allow or deny any permission on a project, doc, play or channel for a role or one person, and see which rule decided what someone can do.

  • Clarify a doc

    A client writes what they need, then answers questions about the gaps on the doc page or their phone until nothing is left, and the answers land in the doc.

  • A welcome wizard for every role

    Newcomers get only the setup steps their roles need, from connecting GitHub to adding their computer, each one skippable, with a red dot in the account menu for what is left. Workspaces start with five ready-made roles, the owner finishes setup without a computer, and Team shows how far each person got.

  • Auto plays

    Plays that start by themselves when a ticket becomes unblocked, changes stage or fails a test, set up from dropdowns on the play, queued per person with bugs first if you say so, and paused by a daily cap.

  • Plays overnight

    Give an auto play a schedule, such as every night at 23:00, and it works through every ticket it takes until a stop time, one at a time on a shared machine if you say so, hands back anything that needs you with a question, and sends one summary in the morning.

  • Faster everywhere

    The web app starts on less than half the code, the phone stops refetching while you scroll chat, and live updates and agent lists fetch only what changed.

  • A new look

    Frosted panels over a soft light field, one ember accent, breadcrumbs and one header on every page, and motion that makes the app feel quick, carried to nexul.io and the phone app.

  • Phone app

    Your inbox, chat, board, docs, deploys and logs on Android or iPhone, signed in by scanning a QR code.

  • Channel webhooks

    Point anything that already posts to a Discord webhook at a Nexul channel instead, by swapping the URL, and manage those bots from the channel's settings.

  • Interview from what you have

    Point a project's interview at its standards, docs, or the project it replaces, confirm the drafted answers, and audit the old code against the new rules.

  • A worktree per thread

    Start each agent thread in its own git worktree, so plays and chats running at the same time never touch the same files.

  • Emoji in chat

    Pick emoji from a searchable picker in the composer, and react to any message with one.

  • Editor tables

    Tables in docs, tickets, memories and notes, written by people or agents, kept as tables both ways.

  • Ticket notes

    The thread sits beside the ticket, and agents leave notes there, a short message with an editable file, instead of growing the ticket.

  • Debugging without the box

    Read the instance's own logs through Nexul or an agent, get told when a service crashes or a stack starts failing requests, let an agent investigate it on a computer that is always on, and turn a bug in Nexul into a diagnosed report.

  • Interview as questions

    Answer a project's interview as question cards, then an agent asks about the gaps and writes the rules every agent turn follows.

  • Change history

    See what changed in a doc, ticket, play, memory or automation, word by word, and put an older version back.

  • Instance templates

    Set the Interview, mention chips, play instructions and ticket bodies once for the whole instance, and copy any of them to another workspace or project.

  • Project access

    Give someone, such as a client, only the projects they need, with what they can do set per project. Everything else stays invisible to them.

  • Private channels

    Channels only the people you add can see and read.

  • Container logs

    Read what a running service prints, live, from the stack page, the canvas, your phone, or an agent.

  • Workspace links

    Every page link names its workspace, and each workspace can have its own WEB project and WEB-1 ticket.

  • Team

    Everyone on the instance in one list, and what each person can reach in every workspace, changed from one place.

  • Devices

    See every browser and phone signed in to your account, sign any of them out, and connect a phone with a QR code.

  • Domain-first setup

    First run gives Nexul its https domain behind a setup code, by Cloudflare tunnel, reverse proxy with Let's Encrypt, or your own HTTPS, before GitHub.

  • Native install

    Every part of Nexul runs as a native service on one port, with no containers of its own.

  • Per-runner credentials

    Each runner enrolls for its own credential, and Remove uninstalls it from its machine.

  • Automations hosts

    Run automations on named hosts on any machine, and choose which host runs each one.

  • Guided agent setup

    A wizard that pairs your computer, sets up your coding harness, and installs Nexul's skills, with a transcript that reads like a run.

  • Tickets that carry the testing

    Blocked-by and found-in links, bug flows, templates per ticket type, and a pass or fail step before done.

  • One-command install

    One command installs Nexul on Linux, macOS, or Windows and opens the setup wizard.

  • Instance upgrade

    Settings shows the newest release, and one click upgrades every service on the server.

  • Plays

    One-button agent runs from a ticket or a doc, on your own coding harness, with your permissions.

  • Memories

    Versioned notes for agents, per project, that agents can write too.

  • MCP server

    Every capability as a tool, with the same permissions as the person who connected.

  • Voice

    Voice rooms with full-screen screen share and camera, on a LiveKit server you run. A call ends for you after five minutes alone.

  • Chat

    Channels, direct messages, and one thread per ticket and per doc, with clickable links and Enter to send.

  • Automations

    Event-driven TypeScript, scoped to a workspace, each automation acting through its own scoped token and switched on or off per workspace.

  • Topology

    A canvas of every service, network, gateway, and hostname, with live status.

  • DNS and tunnels

    Cloudflare records and tunnels, so a service can go live with no open ports.

  • Stacks and deploys

    A runner deploys your compose file, with history, preview branches, and one-click rollback.

  • Runners

    A small binary on each server that connects out, so Nexul never holds an SSH key.

  • Live collaboration

    Several people edit one doc at once, with live cursors and merged edits.

  • Docs and tickets

    Versioned docs in folders per project, with watchers, pinned docs and a resizable list, a board per project, and tickets linked to branches and pull requests.

  • Desktop app

    A desktop shell that keeps a list of your instances and opens the one you pick.