ompjob #

Detached, reboot-surviving, interactive AI agent sessions on a Windows machine.

Start an omp agent over SSH, close your laptop, fly somewhere, reconnect days later, and continue the same conversation — history intact, agent still working.

ssh myhost
ompjob start refactor -Prompt "Migrate the auth module to JWT" -Attach
# ...talk to it, Ctrl+D to detach, close the terminal, shut down your laptop

# next week, from anywhere:
ssh myhost
ompjob attach refactor      # full history replays, then live -- keep talking

The problem it solves #

You SSH into a machine and start a long agent task. Then you close the terminal — and it dies. On Linux you would reach for tmux. On Windows there is no equivalent that works: your agent is a native Win32 process, so a Linux multiplexer inside WSL cannot truly supervise it, and the WSL VM is torn down after ~60s of inactivity or on any wsl --shutdown.

ompjob solves it with the mechanism Windows actually provides.

graph TB
  subgraph task["Scheduled Task, LogonType=S4U"]
    B2["broker.js<br/>owns the agent, serves the pipe"]
    B3["omp --mode rpc<br/>never exits"]
    B2 <-->|JSONL over stdio| B3
  end
  B4["attach.js<br/>you, on Monday"] <-->|named pipe| B2
  B5["attach.js<br/>you, on Friday"] <-->|named pipe| B2
  B2 --> B6[("transcript · render.log<br/>status.json · session/")]

The Scheduled Task is what survives: LogonType=S4U runs whether or not anyone is logged on, needs no stored password, and an AtStartup trigger brings jobs back after a reboot. The named pipe is what makes it interactive: the agent's lifetime is decoupled from any client's, so you attach and detach as often as you like.

What survives what #

Install #

git clone https://github.com/AdityaIndoori/ompjob.git
cd ompjob
.\install.ps1              # adds an `ompjob` function to your $PROFILE
. $PROFILE                 # reload (or open a new shell)
ompjob list                # should print "no jobs"

The shim points at your clone, so git pull updates the tool in place.

Job state lives in C:\ompjob by default. Relocate it with an environment variable if you prefer another drive:

[Environment]::SetEnvironmentVariable('OMPJOB_ROOT', 'D:\ompjob', 'User')

Your first job #

cd C:\some\project
ompjob start hello -Prompt "List the files here and tell me what this project is" -Attach

You are now attached. Type to talk. Then:

Anything else you type goes to the agent. If the agent is mid-task your message steers it immediately — you do not have to wait for it to finish.

Prove it really is detached #

Do not take the claim on faith. Verify it:

# 1. start something slow
ompjob start proof -Prompt "Run bash 'sleep 120', then reply DONE"

# 2. hard-kill the connection from your LOCAL machine (not a clean logout)
#    Windows:  taskkill /F /IM ssh.exe
#    macOS/Linux: pkill -9 ssh

# 3. reconnect and look
ssh myhost
ompjob status proof

Expected: state waiting or thinking, broker live, and attached 0 client(s) — the agent is alive with nobody connected.

Commands #

start flags #

Job states and recovery #

interrupted jobs are also revived automatically at next boot. If you do not want that, ompjob rm <name>.

What "interactive" means here #

You steer the agent. The agent never asks you questions — omp's ask tool does not exist in RPC mode, so a job can never block waiting for a human. That is deliberate: an unattended job that stops for input would hang forever.

Practically: send corrections whenever you like, and they land mid-task.

Troubleshooting #

started '<job>' but the broker pipe has not appeared yet omp is missing, not on PATH, or not authenticated. Verify with omp -p "say OK". Then ompjob logs <name> and check err.log in the run directory.

Four Missing closing '}' errors from a .ps1 you just edited You introduced a non-ASCII character. PowerShell 5.1 reads BOM-less UTF-8 as Windows-1252, so an em-dash becomes â€" and that embedded quote terminates a string. Keep .ps1 files pure ASCII. Check before running:

$e = $null
[System.Management.Automation.PSParser]::Tokenize((Get-Content .\ompjob.ps1 -Raw), [ref]$e)
$e   # must be empty

scp fails with dest open ... No such file or directory Use scp -O when copying to a Windows host whose shell is PowerShell. The modern SFTP protocol mishandles D:-style paths.

Register-ScheduledTask: No mapping between account names and security IDs Your $env:USERDOMAIN does not resolve (common on Microsoft accounts and workgroup machines). ompjob avoids this by resolving your SID at runtime — if you see it, you are calling Register-ScheduledTask yourself somewhere.

ompjob attach says there is no live broker Check ompjob status <name>. interrupted → ompjob revive. finished → the job is over; read it with ompjob logs.

How it works #

broker.js spawns omp --mode rpc and speaks newline-delimited JSON to it over stdio. It translates RPC frames into a render log and serves them to any client on \\.\pipe\ompjob-<name>.

The interactivity primitive is omp's steer command: a message injected into a live streaming turn. The broker routes automatically — steer while the agent is working, prompt while it is idle — which is what makes typing at any moment behave like an ordinary conversation.

Everything durable is on disk under the job root, so reattaching after a reboot works: transcript.jsonl (every RPC frame), render.log (the replay backlog), status.json (reconcilable state), session/ (omp's own session, for -c).

Files #

Documentation #

Hosted at ompjob.aindoori.com, generated from this repository's own markdown so it can never drift.

License #

MIT — see LICENSE.