Run agents on a timer, start them when a file changes, add your own steps around them, or record a routine and replay it. They are the same agents you run by hand, working without you at the keyboard.
Nightly dependency audits, morning triage sweeps, weekly doc refreshes - agent tasks on a cron schedule, results filed as cards in the Vault before you sit down.
File-system and event watchers dispatch agents when something changes - a failing test, a touched schema, a new PR. The watcher is the trigger; your hooks and your review decide what lands.
Run your own checks before and after agent actions - block a commit, require a lint pass, notify a channel. Hooks are yours; agents can't skip them.
Record a UI sequence once - pane layout, commands, dispatches - and replay it as a one-keystroke macro. Your morning setup becomes a single action.
Say what you want built. Orcyx plans it, sets up the project, builds it and runs the checks itself, then a fresh reviewer has to accept the evidence before the work lands in your project. Anything that publishes, sends or pays still asks you first.
A new seat is equipped for the job it was given - matching skills attached, hooks and MCP servers suggested. A running pane only ever gets a suggestion, nothing is mutated under you, and a matcher that fails says so instead of skipping quietly.