A roadmap with
clear states.

Bring the workspace together.

The installed controller and private dashboard provide the starting point for team coordination.

• Attributed messages, supported queue/wake/steer routes.
• Saved conversation logs and available-history export.
• Organization and project views, usage observations, local Ollama routes.
• Encrypted provider-key settings, with live key validation still pending.

Commands from the website.

Make the dashboard a practical place to send messages, wake supported chats, and steer running work.

• Deploy the prepared command flow to the private site.
• Verify browser-to-chat replies on registered local Codex routes.
• Show explicit errors, delivery states, and a safe recovery path.

More complete connections.

Improve provider-specific messaging and history without hiding where a source remains incomplete.

• Validate additional ChatGPT and Claude routes independently.
• Expand available history where the upstream source allows it.
• Add bounded background refresh and dependable freshness indicators.
• Improve usage collection while preserving source and timestamp.

Setup that travels well.

Turn the existing package into a setup process that can be accepted on a second machine.

• Check account, path, certificate, and roster setup on a fresh installation.
• Verify startup and recovery after a full reboot.
• Test isolated restoration, upgrades, and rollback.
• Publish practical setup and maintenance documentation.

A dedicated private room.

Use swarmcord.com for public product information and swarmcontrolla.com for the private workspace.

• Evaluate Cloudflare Access for the required private login rules.
• Keep certificate authentication available.
• Define email one-time codes and authenticator-code options before enabling them.
• Give the owner explicit control over optional login methods.

Authentication methods will be described as available only after configuration and end-to-end testing.