Run scheduled agent jobs for server upkeep
A developer triggers Codex from cron to install updates, check for vulnerable software, and inspect logs on servers.
- What they did
- The developer set up cron to start Codex sessions on a schedule, with their own harness handling the wrapper work. Each session deals with server maintenance tasks: patching the machine, surfacing vulnerable packages, and scanning logs for traces of suspicious access. The harness stores a running plan on the filesystem, passes information forward to the next session, and clears out prior context before the next run.
- How it went
- The process is already in use, but the source does not give any outcome numbers or incident details. The developer would prefer the custom harness to take over from Codex later, since they are concerned about dependencies and supply-chain exposure.
- Tips
- Decide ahead of time what the agent is allowed to do on the server. Add a human check before any reboot, deletion, or other change that cannot be easily undone.
Try it yourself with Codex
On [server name or SSH alias], create a cron task that launches an agent at [time or interval] to install available security patches, identify any packages with known vulnerabilities, and examine [log files or paths] for possible unauthorized access, including repeated login failures or traffic from IPs that do not look familiar. Save a short text report to [file path or email address], then stop. Before anything runs, show me the cron rule and the exact commands you plan to execute, and wait for my approval. Do not reboot, remove files, or send anything without asking first. If you need to preserve state between runs, write it to [path].
Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.
Get 3 agent uses like this every morning
With the day's top AI news. Free, and one click to unsubscribe.
Related agent uses
Port a computer-use tool into another harness
They had Gemini rework Codex’s computer-use tool for Antigravity and finished the port in under 10 minutes.
Let Codex implement while you handle planning
One person used ChatGPT for planning and Codex for execution, with a small port helper to keep parallel local runs from colliding.
Build a local app for agent output cleanup
They used Codex to create Mianotes, a local place to collect agent-made files and links.
Ask Codex for five admin screen redesigns
A developer used Codex CLI to create five alternative admin-screen designs and then chose the one they preferred.
Run work coding and support tasks through agents
A consultant uses Claude, Codex, and a custom containerized harness to handle client software work and a personal assistant project.
Run several coding agents from one interface
A developer uses T3 Code to manage multiple coding agents on personal machines, a VPS, and a separate work setup for code changes and writeups.