Host identity
Display the machine and checkout associated with the session so local and remote work are not confused.
Work with repositories on machines you control. Keep the browser light and the agent close to the code, tools and compute it needs.
A development server can hold the dependencies, disk space and long-running processes that do not belong on every laptop. Qodarium's local and remote host model is designed to let you reach that environment from a consistent workspace.
SSH is the connection boundary for remote projects in the product scope. The remote host still needs the runtime, repository access and resources required by the task. A web interface does not remove those dependencies.
Display the machine and checkout associated with the session so local and remote work are not confused.
Run code and tools on your infrastructure rather than assuming every task belongs in a hosted sandbox.
Validate the agent installation, authentication and project permissions before starting a session.
Treat a lost connection as missing visibility until host-side state has been checked.
Use an account with the permissions the development task needs and no more.
Confirm access to the repository and toolchain through your normal SSH workflow.
Know how to inspect the host and back up project data independently of the browser.
That is a target workflow. Capacity depends on the repository and tools, not just Qodarium's interface.
No. It is a workspace for agent-driven development, not a general production deployment orchestrator.
A workspace that holds the context while you focus on what comes next.