[SushantGautam]

Why

A full pytest -m "not embedded_hatchet" run overwrote the workspace model studio.agent-1 of the Open WebUI that a local manage.py dev serves on 127.0.0.1:8080 (name "Prompted Agent", base model 1.model-123, from AgentUITest::test_agent_prompt_picker_renders_as_list_and_resolves_version).

Root cause: .env is not loaded under pytest (only manage.py calls load_dotenv). 23 tests patch chat.config.ENABLED = True without mocking the HTTP layer, while chat.config.UPSTREAM keeps its default http://127.0.0.1:8080/chat. Agent/KB/tool syncs, ChatAPI.sign_in and trace_target._owui_get_jwt then hit whatever listens there. In CI nothing does, so the connection is refused and the tests pass, which is why it went unnoticed.

A related path: one-off manage.py commands in a worktree read the same .env but not the per-checkout SIMPLEAUDIT_CHAT_UPSTREAM that manage.py dev exports, so they fall back to :8080, which is the main checkout's Open WebUI.

What changed

• simpleaudit_studio/no_live_chat.py: a socket guard that, during tests, refuses every TCP connect to the chat upstream or to loopback :8080. Ports the test process listens on itself (stub servers, e.g. chat/tests/test_proxy.py) stay reachable. conftest.py and manage.py test install it.
• pytest.ini and manage.py test force SIMPLEAUDIT_CHAT=off, so neither a sourced nor a loaded .env can turn chat on for a whole run. Chat tests keep enabling it themselves.
• lifecycle.route_one_off_chat (called from manage.py for non-dev, non-test commands): with chat on and no explicit upstream, it uses this checkout's live dev stack's chat port. When :8080 belongs to another checkout's live stack, it turns chat off for that command and prints a note. An explicit SIMPLEAUDIT_CHAT_UPSTREAM (compose, the dev stack's own children) is left alone.
• Tests: simpleaudit_studio/tests/test_no_live_chat.py covers the guard, plus the original leak (an unmocked agent sync against a foreign listener receives no connection). tests/test_lifecycle.py covers the routing. There is also a short section in docs/chat.md.

Reviewer notes

• The 23 leaky tests are not rewritten. They now get the same refused connection as in CI. Mocking them properly is a possible follow-up.
• _CHAT_DISABLED_VALUES in lifecycle.py mirrors chat.config.DISABLED_VALUES and is not imported from it, because importing chat.config before django.setup() would freeze its settings. A test asserts the two sets match.

Checks

• With SIMPLEAUDIT_CHAT=embedded in .env and exported in the shell, and SIMPLEAUDIT_CHAT_UPSTREAM pointed at a recording server: uv run pytest -m "not embedded_hatchet" -n auto gave 1822 passed and 3 skipped, and the recorder logged 0 requests.
• uv run manage.py test simpleaudit_studio.tests.test_no_live_chat passes with chat enabled in .env.
• uv run ruff check . is clean.
• Not run: -m embedded_hatchet (infra/worker.py and infra/minimal_config.py are untouched).

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.