Know what changed in each container
Review tooling updates by container: who requested them, which versions were found and whether each update succeeded. Agent CLIs, context tools and runtime tools share one paged history; a requested version is never shown as already installed.
How it works
Trace actual tooling changes
Open a bounded page of container history. Agent, context and runtime tools show the actual versions found, request source and outcome; requested versions are not installation evidence.
Inspect automatic review defaults
Keep user defaults and project overrides separate. Review triggers start disabled in this fixture; unknown Git configuration requires explicit manual hook integration.
Review automatic trigger settings
Inspect commit and push-attempt triggers, an optional local push gate, reviewer account, host and model. Leave the real form without saving or launching a reviewer.
Keep blocked review evidence visible
Read synthetic trigger history. Agent-reported completion and a passing exact-subject gate remain separate; this sample starts no paid reviewer.
Choose the managing session defaults
Choose default agent, account, execution host and model for new operator conversations. Existing chats keep their current processes.
Choose Docker or Host execution
Docker keeps the manager in a private container with checked administration APIs. Host runs as the server tooling OS user. This changes the next launch, preserving the current process.
Try the interface
Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.
Watch the workflow
Loading the recorded terminal…
Put your server to work.
Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.