Codex CLI can queue bounded runs in osFoundry team and loop sessions as a Runner

A new guide explains how Codex CLI can act as a Runner inside osFoundry team or loop sessions. From the terminal, Codex queues a bounded objective with request_session_run, and the session's own agents carry out the work on its runtime. Codex then reads the outcome, leaves a note on the session's Team mail, and collects the agents' replies. The owner approves the connection once and assigns the Runner seat per session, so individual runs need no further clicks. Codex is configured to ask for confirmation before any write-capable tool runs, and the owner can remove the seat or revoke the connection at any time.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.




Discussion (0)
Log in to join the discussion and vote.
Log in