Agent threads
Focused Codex threads stay attached to the project they serve.
Agent IDE
Turnless keeps Codex threads, project files, activity, attention requests, and resume state in one workspace so long-running agent work can continue across interruptions.
turnless

Project-native
Each agent thread lives inside a project with its own durable home, shared direction, private thread context, and restart-safe state.
project folder
-> .fray state
-> durable agent homes
-> shared direction
-> private Codex threads
-> attention and resume loopWorkspace surface
Turnless shows agent threads, project files, runtime state, attention requests, and activity views in one operating surface.
Focused Codex threads stay attached to the project they serve.
Direction, files, artifacts, and local state sit around the work.
Each agent has a durable home under `.fray` for continuity.
Running, queued, waiting, stale, and idle work is visible.
Requests for input stay tied to the project and thread context.
Restart-safe state makes long runs recoverable after interruption.
Work loop
Open a project, choose an agent thread, give work, and let the agent write state and artifacts back into the project. Turnless keeps runtime, attention, and activity visible so the thread can continue from the state it already wrote.
01
Open project
02
Choose agent
03
Give work
04
Track activity
05
Reply or resume
Activity and attention
Running, queued, waiting, paused, stale, and idle work appears as project activity. When an agent needs input, the request stays attached to the project and the reply becomes part of the thread context.
running
Agent is writing project state
waiting
Attention request is ready
resumable
Thread can continue after restart
Turnless gives long-running agent work a durable workspace instead of a disappearing transcript.