Codex CLI logo
Codex CLI template
x.comyourmax.ai

Outbound Loop for Codex

Outbound as a dual loop: daily score→draft→log, weekly one-concept tune behind an eval gate. Never auto-sends.

NewNew18.0 KB snapshotStarter VM

What's inside

Harness

Codex CLI

Plan

Starter

vCPU

1

Memory

2 GiB

Snapshot

18.0 KB

How it works · ~3 minutes

  1. 01 · Fork

    New isolated microVM on your subdomain — creator state included.

  2. 02 · Your keys

    Log into Codex CLI with your own model credentials (BYOK).

  3. 03 · Ask it to work

    Open the terminal and give it a real job. You keep what ships.

30-day money-back on your first purchase · no free trial · keys never leave the VM

About this template

Outbound Loop for Codex

This is a loop, not a static outbound kit.

Source: https://x.com/nifinet/status/2078851409068654639

Loop 1 — Run (every touch)

sense → score → draft → human sends → log outcome
  • /outbound-loop — full touch cycle (score + draft; no send)
  • /outbound-score / /outbound-draft — single steps
  • Append ~/outbound-loop/memory/outcomes.jsonl with a real reason when the market answers

Loop 2 — Tune (weekly only)

read outcomes → one file change → eval gate → PR → human merges
  • /outbound-tune
  • Gate: python3 ~/outbound-loop/evals/score.py → one number
  • One concept per proposal. Thin samples → no change.

Loop 2 edits the files Loop 1 runs on. That is the product.

BYOK

codex login
# or: codex login --device-auth
# or: export OPENAI_API_KEY=sk-...

Sending and merging stay human. Replace sample outcomes with yours before trusting weekly tune.

Inside this fork

Forking copies this template into a brand-new, fully isolated microVM on your own subdomain. Here's exactly what lands in it.

  • Codex CLI agent

    The upstream harness, pre-installed — same version the creator ran.

  • Starter VM

    1 vCPU · 2 GiB RAM · 10 GiB disk.

  • Creator's /persist data

    The captured persist volume is copied byte-for-byte into your fork.

  • BYOK — your keys, your VM

    Add your model API keys after forking; they live only inside your microVM.

What you'll configure after forking

Secrets are scrubbed from shared templates — these are the names you supply in your agent's terminal once it boots.

Environment variables

  • OPENAI_API_KEY

Your turn

Your own Outbound Loop for Codex, live in about 3 minutes.

Forking copies this Codex CLIagent into a brand-new, fully isolated microVM on your own subdomain — the creator's /persist state and all. Add your own keys after it boots; they never leave the box. Don't love it? Your first jurniti purchase comes with 30 days to get every cent back.

New paid VM · BYOK · 30-day money-back on your first purchase · ~3 min to provision

Starter · fork

$25/ mo

Needs 1 of your own API key