Warden
A self-hosted web development environment with editor, terminal, account and coding-agent workflows.
Open Warden at my.warden.cv.
No configured instances: my.warden.cv immediately opens localhost:7332, so a normal single local installation needs no launcher setup.
One configured instance: it opens that named instance directly. Two or more: it shows the instance catalog, with each entry storing a name, domain/IP and optional port.
The configuration remains browser-local and can be opened directly even when normal launcher navigation redirects. The planned my.gantry.cv app drawer links into these per-project launchers rather than copying their instance registries.
A development workspace you can host on the machine doing the work.
Warden turns a server, workstation or development box into a browser-accessible development environment. It combines project editing, terminals, user access and agent workflows so remote development does not have to mean stitching together SSH sessions, an unrelated file browser and a separate chat window.
The application is deliberately useful for one person on one machine, but its account model also supports multiple Warden users and administrator roles. Authentication, permissions and provider credentials belong to the environment rather than being assumptions pushed onto the surrounding network.
Warden is not intended to make local tools obsolete. It is for the cases where the development machine is somewhere else, needs to stay running, or benefits from a persistent browser workspace that can be reopened from another device.
Useful capability without mandatory complexity.
The project stays focused on its own job; the surrounding Gantry tools remain optional.
Edit real project files with familiar panes, shortcuts and contextual actions instead of treating the editor as a thin textarea in front of a shell.
Keep concurrent shell work separated and close to the project rather than reusing one terminal process for unrelated tasks.
Agent sessions sit beside editor and terminal workflows so code, commands and reasoning belong to the same development environment.
Accounts, roles, two-factor authentication and provider controls make a shared self-hosted machine practical without assuming every visitor is the same OS user.
Start with the shortest path.
Advanced deployment or integration features appear only when the workflow actually needs them.
- 01
Run Warden directly during development, or install its service when the workspace should survive terminal closure and logouts.
- 02
Open
my.warden.cv. Zero configured instances goes tolocalhost:7332; one configured deployment opens directly; several present a named chooser. - 03
Open a project, use the editor and terminals normally, and invoke the agent where it saves work rather than making every action agent-mediated.
- 04
For a machine already represented in Watchpost, jump straight from the monitored host to Warden in a new tab when the incident needs hands-on editing or terminal work.
Connections that remove real hand-off friction.
Each product already owns one side of these workflows. The integration exists to remove duplicate navigation, setup or context.
Cortex
Cortex and Warden overlap deliberately at the agent/workspace boundary. Cortex is the smaller standalone agent surface; Warden is the full remote development environment. Durable sessions, terminal management and agent UX can be shared architectural lessons without erasing the product boundary.
Explore Cortex →Watchpost
A Watchpost machine can carry a Warden association. From an incident or host view, “Open Warden” preserves Watchpost in the current tab and opens the development environment separately, making the jump from diagnosis to hands-on repair almost frictionless.
Explore Watchpost →Nift
Warden is a natural environment for Nift sites because Nift is fast enough for tight edit/build/reload loops and produces ordinary files that are easy to inspect from the same workspace.
Explore Nift →Trestle
Develop a Trestle-backed application in Warden while the backend runs locally or remotely. Trestle remains independently deployable; Warden simply provides the development surface around the application using it.
Explore Trestle →Where Warden earns its place.
Use a stronger server or always-on NUC as the development machine while keeping the interface in your browser.
Give several users controlled access to one self-hosted development environment.
Open the exact monitored machine from Watchpost and move directly into editor/terminal work without losing the alert context.
Explore Warden.
Project-specific installation, commands and release details live on the project site.