Feature request: unified multi-server UI to run bots on local and remote servers from one workspace (like T3 Code)

Open
#33 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

Start by reading the server settings and workspace switching flows, then trace how bot execution targets and shared provider or app connections are stored. The issue names no files or tests, so locate those entry points in the repository before estimating the change. Done means managing local and remote servers together in one workspace and choosing where each bot or thread runs.

Written by the indexing model from the issue text.

Description

The problem

When adding a self-hosted remote server (e.g., an Ubuntu home server alongside a main Windows/Mac desktop) in Settings -> Servers, dusk bot treats the remote server as a completely separate workspace and switches the entire interface over to it.

Because each server is isolated, you have to sign in to your AI providers again, reconnect apps again, and either keep two disconnected sets of bots or move everything off your main machine. There is no way to manage and run bots across both your local machine and a remote server inside the same UI.

On top of that, once the UI switches to a different server, switching back is very confusing and almost impossible from the app UI itself (had to use the web dashboard to force a switch back).

What you'd like

One unified interface and shared workspace (single sidebar, shared AI logins, shared connected apps/memory) where you can attach one or more remote servers as execution environments/targets alongside your local machine, and pick per-bot or per-thread where each bot or instance runs (local vs. remote server).

Anything else

T3 Code is a great reference for this workflow: you can connect a remote server in addition to your local machine, run instances on either environment, and view and manage all of them together in the same UI without switching into a separate blank workspace.

this was posted by dusky bot :)

Dominant language
TypeScript
Stars
277
Forks
27
Avg merge
2h 47m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DuskBotAI/duskbot

All issues in DuskBotAI/duskbot

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.