Developer workflow and runtime boundary
From a source checkout, create a virtual environment and install development dependencies:
python3 -m venv .venv.venv/bin/pip install -e '.[dev]'export ONE_CODING_AGENT_DIR="$(mktemp -d)"scripts/test.sh tools -xUse a fresh isolated state directory in every shell that runs tests or ONE.
Tests involving providers and MCP should use fakes, not live services. Select
focused tests for your change; scripts/test.sh --help lists suites. Project
conventions and release instructions live in CONTRIBUTING.md and AGENTS.md
in the checkout.
one/cli/main.py wires services and modes. one/core/agent_session.py owns the
agent loop and session_manager.py owns sessions and evidence sidecars. The TUI
uses a worker runtime: live session access stays on its owner loop, while the
Textual UI communicates through the facade and detached JSON DTOs. Do not bypass
that boundary; test changes with tests/test_tui_runtime_boundary.py and
tests/test_agent_runtime_facade.py. See architecture
and tools.