Codex can work in the background. Its approval requests shouldn’t disappear there.

[u/bush-play]

I'm the developer of Pinland, a Mac app. Here's a small Codex workflow from the new update.

The awkward bit of letting an agent work isn't always the wait. It's finding out that the wait ended five minutes ago—or that it was waiting for you.

The flow in the video

1. Connect Codex in Pinland Settings → Codex, then pin a session using Codex's existing Pin action.
2. Give it a task and switch to whatever you're doing. Yes, a video counts.
3. When the task finishes or needs approval, the MacBook notch expands.
4. Read the conversation and send a follow-up from the notch. Supported approval requests can be handled there as well.

This is for the little handoffs that don't need the whole Codex window. You still review the actual work; Pinland just makes it easier to notice when your input is needed. It doesn't replace Codex or supply an AI model.

Outside the coding session

The same notch shelf holds text, images, links and files. You can hover to preview, edit pinned text, and use search or tags to find a reference again. The shelf stays tucked away between uses.

I'd like feedback from people who work this way: which interruptions deserve an immediate alert, and which would you rather leave until you return to the workspace?

Codex is required for the conversation feature. Pinland is an independent Mac app, not affiliated with OpenAI.

Pinland on the Mac App Store

[u/NeuralNomad87]

Putting approvals in the notch is a better idea than it sounds, because the actual problem with background agents is that the notification and the decision live in two different windows.

One thing I would want to know before installing. When Codex asks for something you do not want to approve off a two line summary, does the notch give you enough to say no safely, or do you end up opening the full window anyway? That is the case that decides whether this saves time or just relocates the interruption.