# `MingaClaudeBridge.Route.Config`
[🔗](https://github.com/jsmestad/minga-claude-bridge/blob/main/lib/minga_claude_bridge/route/config.ex#L1)

The processes and settings `MingaClaudeBridge.Route` uses.

Minga calls the route callbacks without any bridge-specific argument, so `load/1` starts from the defaults below, applies the `:minga_claude_bridge, :route` application environment, then the given overrides. Tests pass a config directly to `MingaClaudeBridge.Route.stream/2` and `MingaClaudeBridge.Route.availability/3` to use the scripted transport and per-test processes.

  * `:transport` - `{module, opts}` for every session. Defaults to the real `claude` Port.
  * `:registry`, `:supervisor`, `:status`, `:tasks` - the conversation registry, the session supervisor, the status server, and the task supervisor started by `MingaClaudeBridge.Supervisor`.
  * `:session_opts` - extra `MingaClaudeBridge.Session` options, for example `:idle_timeout`.
  * `:probe_timeout` - milliseconds a probe waits for Claude Code's `initialize` answer.
  * `:measure_deadline` - milliseconds a background measurement (plan usage and context windows) may run, including its own Claude Code startup.
  * `:window_ttl` - milliseconds a measured context window stays fresh. Defaults to 24 hours.
  * `:availability_ttl` - milliseconds an availability result is reused.

# `t`

```elixir
@type t() :: %MingaClaudeBridge.Route.Config{
  availability_ttl: non_neg_integer(),
  measure_deadline: pos_integer(),
  probe_timeout: pos_integer(),
  registry: atom(),
  session_opts: keyword(),
  status: GenServer.server(),
  supervisor: GenServer.server(),
  tasks: GenServer.server(),
  transport: {module(), keyword()},
  window_ttl: non_neg_integer()
}
```

# `load`

```elixir
@spec load(keyword()) :: t()
```

Builds the config from the defaults, the application environment, and `overrides`.

---

*Consult [api-reference.md](api-reference.md) for complete listing*
