Struct ServeArgs 

pub struct ServeArgs {
    pub port: u16,
    pub host: String,
    pub cors: Option<String>,
    pub token: Option<String>,
    pub allow_admin: bool,
    pub workdir_root: Option<PathBuf>,
    pub tls_cert: Option<PathBuf>,
    pub tls_key: Option<PathBuf>,
    pub no_remote_yolo: bool,
}

Arguments for lev serve.

Fields

port: u16

Port to listen on

host: String

Host to bind to

cors: Option<String>

Allow browser requests from this origin (e.g. http://localhost:5173).

Defaults to none: the API is for programmatic clients, which are not subject to CORS at all, so a browser-facing default of * gave nothing to the normal case and widened the surface for the unusual one. A dashboard served from another origin sets this explicitly.

* is still accepted and still means “any origin”. It is now a decision someone typed rather than what you get by not thinking about it.

token: Option<String>

API token clients must present (Authorization: Bearer <token>, or ?token= for WebSockets). Overrides the LEVIATH_API_TOKEN env var; the server refuses to start if neither is set.

Prefer the environment variable: an argument is visible in ps to every local user for the lifetime of the process.

allow_admin: bool

Enable the MCP administration endpoints (POST/DELETE /api/mcp/servers).

Off by default, because they are remote code execution by construction. Adding an MCP server writes a command and args into ~/.leviath/config.toml, and Leviath then spawns exactly that - so any token holder could run an arbitrary process, persistently, for every future run. The rest of the API can only run agents the user already installed; this one adds new executables to the machine.

workdir_root: Option<PathBuf>

Restrict agent working directories to this root.

Without it, POST /api/agents accepts any workdir - including / - so a token holder can point a tool-executing agent at the whole filesystem. Set this to the directory the API is meant to work in.

tls_cert: Option<PathBuf>

PEM certificate chain to serve HTTPS with. Needs --tls-key too.

Bring your own; Leviath never generates one. Without HTTPS the browser console cannot reach a lev serve that is not on loopback - the browser blocks the request before sending it, so no server-side header and no --cors value can help. A LAN address is blocked exactly like a public one.

mkcert and tailscale cert both produce certificates that work here. See the “reaching a Leviath on another machine” section of the docs.

tls_key: Option<PathBuf>

PEM private key for --tls-cert. Needs --tls-cert too.

no_remote_yolo: bool

Refuse "yolo": true and "allow": [...] on spawn requests, so an API caller cannot waive approval prompts for an agent running on the host.

Both fields, because they are one lever: "allow": ["*"] reaches the same wildcard override "yolo": true writes.

Trait Implementations

impl Args for ServeArgs

fn group_id() -> Option<Id>

Report the ArgGroup::id for this set of arguments

fn augment_args<'b>(__clap_app: Command) -> Command

Append to Command so it can instantiate Self via FromArgMatches::from_arg_matches_mut

fn augment_args_for_update<'b>(__clap_app: Command) -> Command

Append to Command so it can instantiate self via FromArgMatches::update_from_arg_matches_mut

impl Clone for ServeArgs

fn clone(&self) -> ServeArgs

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl FromArgMatches for ServeArgs

fn from_arg_matches(__clap_arg_matches: &ArgMatches) -> Result<Self, Error>

Instantiate Self from ArgMatches, parsing the arguments as needed.

fn from_arg_matches_mut( __clap_arg_matches: &mut ArgMatches, ) -> Result<Self, Error>

Instantiate Self from ArgMatches, parsing the arguments as needed.

fn update_from_arg_matches( &mut self, __clap_arg_matches: &ArgMatches, ) -> Result<(), Error>

Assign values from ArgMatches to self.

fn update_from_arg_matches_mut( &mut self, __clap_arg_matches: &mut ArgMatches, ) -> Result<(), Error>

Assign values from ArgMatches to self.