An operational runtime for Codex

Codex can do the work. Orkestr keeps it moving.

One persistent Codex workstation you can reach from the browser or WhatsApp, trigger manually or on a schedule, and supervise through a live Ubuntu desk.

See the real workflow View the source
Self-hosted with Docker Codex + GPT-5.6 One continuous conversation Real screenshots
Orkestr Chat showing a real GPT-5.6 research request in one continuous Codex conversation
Start the work Browser, WhatsApp, or a one-time, hourly, daily, weekly, or cron schedule.
Codex keeps the context One queue, one conversation, one Ubuntu workstation, and the same files and browser state.
Stay in control Watch the desk, take over when needed, and receive the result wherever the work began.
One real run

The task changes. The operating loop stays.

This run uses a sourced research task because it forces the whole system to work: browser research, files, a phone follow-up, and a scheduled return to the same context.

01 · Connect

Bring your own Codex account.

Docker is already running. Connect Codex, optionally link your own WhatsApp account, and open one private workstation. No second bot account and no public hosted agent are required.

Workstation setup with Codex and WhatsApp connected
02 · Execute

Give Codex a real computer.

Codex works inside a persistent Ubuntu desk with Chromium, terminal access, and the shared workspace. Watch it live, pause it, or take control without breaking the conversation.

Live Ubuntu Desk with the generated research report open in Chromium
03 · Keep the output

The work stays usable.

The report is not trapped in a chat reply. Its Markdown and HTML files stay in the workstation, where you can inspect, download, continue editing, or send them to WhatsApp.

Workstation Files view containing cited Markdown and HTML reports
04 · Continue from your phone

WhatsApp is part of the same conversation.

Here, the user asks for a follow-up from WhatsApp. Codex keeps the existing research context, updates the report, and returns the actual Markdown file to the same chat.

WhatsApp self-chat showing a Codex follow-up and a returned Markdown document
05 · Return on schedule

Recurring work does not need another system.

A weekly source review is scheduled and run through the same queue. The result returns to the existing conversation and is mirrored to WhatsApp. Manual requests and timers do not create disconnected agent histories.

Timers view with a weekly Codex source review The scheduled source review completed in the same Codex conversation
Built for operational work

Use the same loop wherever consistency matters.

Outreach Research contacts, prepare follow-ups, and return drafts for review.
Job search Review opportunities, prepare materials, and revisit the pipeline.
Messaging Inspect unresolved threads and bring decisions back to the human.
Recurring checks Inspect sites, reports, queues, or repositories on a schedule.