The dedicated provider guide and nav entry are sufficient discovery;
listing it on the curated overview page alongside OpenAI/Anthropic/
Vertex elevates it past its actual tier.
- Revert README providers list to original wording (no Novita prepend)
- Move Novita to the bottom of the LLM Providers nav (after Azure)
- Move Novita card below the cloud providers in the overview
- Drop '(recommended)' annotation from Kimi K2.5 in the model table
The overview table lists Novita alongside providers that only need
STRIX_LLM + LLM_API_KEY, but Novita also requires LLM_API_BASE to
point at api.novita.ai/openai. Without this, users copying the generic
code block would hit connection errors against api.openai.com.
Add a Note callout directing users to the Novita guide for full setup,
and mention Novita in the README supported-providers reference line.
Re-architects the agent loop to support interactive (chat-like) mode
where text-only responses pause execution and wait for user input,
while tool-call responses continue looping autonomously.
- Add `interactive` flag to LLMConfig (default False, no regression)
- Add configurable `waiting_timeout` to AgentState (0 = disabled)
- _process_iteration returns None for text-only → agent_loop pauses
- Conditional system prompt: interactive allows natural text responses
- Skip <meta>Continue the task.</meta> injection in interactive mode
- Sub-agents inherit interactive from parent (300s auto-resume timeout)
- Root interactive agents wait indefinitely for user input (timeout=0)
- TUI sets interactive=True; CLI unchanged (non_interactive=True)
The perplexity API key check in strix/tools/__init__.py used
Config.get() which only checks os.environ. At import time, the
config file (~/.strix/cli-config.json) hasn't been applied to
env vars yet, so the check always returned False.
Replace with _has_perplexity_api() that checks os.environ first
(fast path for SaaS/env var), then falls back to Config.load()
which reads the config file directly.
Users can now access the Caido web UI from their browser to inspect traffic,
replay requests, and perform manual testing alongside the automated scan.
- Map Caido port (48080) to a random host port in DockerRuntime
- Add caido_port to SandboxInfo and track across container lifecycle
- Display Caido URL in TUI sidebar stats panel with selectable text
- Bind Caido to 0.0.0.0 in entrypoint (requires image rebuild)
- Bump sandbox image to 0.1.12
- Restore discord link in exit screen
The badge image URL used invite code which is expired,
causing the badge to render 'Invalid invite' instead of the server info.
Updated to use the vanity URL which resolves correctly.
Fixes#313