Running a server¶

Starting¶

gdc serve --bind 127.0.0.1:8088
gdc-tui --bind 127.0.0.1:8088

The server provides session HTTP endpoints and WebSocket agent execution. A provider is needed for runs, but stored-session inspection is provider-free.

Common options¶

Flag	Default	Effect
`--bind ADDRESS`	`127.0.0.1:8088`	Listen address; also `GDC_SERVE_BIND`
`--profile NAME`	`default`	Initial agent profile
`--output-style NAME`	Configuration value	Reply style
`--db-path PATH`	Storage configuration	Session database
`--role ROLE`	Unset	`orchestrator`, `worker` or `both`

See CLI reference for all server flags.

Encrypting connections¶

Use a certificate/key pair, ACME, or self-signed swarm TLS. See TLS.

Exposing beyond the local machine¶

Non-loopback binds require both --role and configured TLS. Swarm identity setup is also required for swarm roles. Session endpoints still need an authenticating proxy or equivalent access restriction. For remote personal use, keep the server on loopback and tunnel:

ssh -L 8088:127.0.0.1:8088 server-host
gdc-tui --bind 127.0.0.1:8088

See Security.

Coordinated work durability¶

[task]
resume_interrupted_workers_on_startup = false
idle_timeout_secs = 0

Setting	Behavior
Startup sweep	Mark orphaned running workers interrupted
Resume enabled	Restart interrupted workers
Positive idle timeout	Archive terminal worker records after inactivity
Idle timeout `0`	Disable the archive reaper

Root sessions are not part of the worker sweep. See task configuration.

Stopping¶

Send Ctrl+C or stop the process through its supervisor. Completed messages remain persisted; inspect interrupted work before resuming operations that may have produced external side effects.