5.5 Updating, stopping and removing
The commands
| Command | What it does |
|---|---|
casbin-gateway start | Starts the server in the background |
casbin-gateway stop | Stops it |
casbin-gateway status | Says whether it is running, and where |
casbin-gateway | Runs it in the foreground, stopped with Ctrl-C |
casbin-gateway uninstall | Puts back everything Gateway wrote outside its own directory |
All of them work from any directory: the command is a wrapper that always starts Gateway in its install directory, where its data lives.
In the background, console output goes to logs/casbin-gateway.out.
Updating
The version Gateway is running sits in the top-right corner, with the date it was built, and says New when the published build is a later one.
Open it and press Update now: Gateway downloads the build for this machine, checks that it runs, puts it in place of itself and restarts into it. The page reloads on the new version when it comes back.
Nothing else has to be touched — the data, the settings and the casbin-gateway command all stay where they are.
Gateway installed some other way, or in a directory it cannot write to, says so and shows the install command to run by hand instead. Running the install command again is always a valid upgrade; your database and settings are untouched either way.
Removing it
Run casbin-gateway uninstall first.
Deleting the directory is the part you can do yourself. What that cannot undo is everything Gateway wrote outside it:
- the monitoring hooks in every agent's own configuration,
- the provider each agent was pointed at,
- the login entry,
- the desktop entries,
- and the
ccswitch://scheme registration,
all of which would otherwise be left naming a program that is no longer there.
uninstall puts all of that back, then names the two things to delete by hand:
| Platform | Delete |
|---|---|
| Linux, macOS | ~/.local/share/casbin-gateway and ~/.local/bin/casbin-gateway |
| Windows | %LOCALAPPDATA%\casbin-gateway and its PATH entry |
The agents themselves, their sign-ins and their history are left exactly as they were.
5.4 Docker and Podman
Agents are discovered by reading the home directories and install paths of the machine Gateway runs on, and inside a container that is the container's own filesystem. So Agents, Skills, MCP & Prompts and agent monitoring stay empty there — and the pages say so, rather than pretending nothing is installed.
6.1 Frequently asked questions
Next Page