Concierge

Concierge sits at the top of the rail, above your fleet and slightly apart from it. It is a Claude session like any other, with one difference that shapes the whole app: it can see every project Nightdesk watches, reach any agent in the fleet, and file a task in any of them.

It is how you ask for things

Nightdesk has no New Project dialog and no Create Task form. Where another app would hand you a sheet with fields in it, Nightdesk hands you Concierge: you tell it to start watching a repository, or to file a task, or to give a task to an agent, in the words you would use with a person.

Launching a session is the exception: it has a sheet of its own, where you choose a checkout and an account.

Its row

Concierge’s row has the same shape as every other row on the rail: the name on a pill in its own color, its status, its model and thinking level, and its context badge. It is anchored above the list, so it never moves as the fleet reorders underneath it. At rest it reads Not running.

Its subagents appear indented beneath it exactly as any agent’s do, and leave when they end.

Starting it, and what it remembers

Press ⌘0, or click the row, to put Concierge’s terminal in the center column. The session starts the first time you go there rather than when Nightdesk launches.

Concierge is one continuing session. Quitting Nightdesk and coming back resumes the same conversation rather than beginning a new one, so what you told it yesterday is still there. It runs on Opus 5 at high effort, and compacts itself at a fixed budget rather than waiting for its context window to run out. That budget is a deliberate ceiling on what a session that never ends costs you in money and in waiting, not a guard against the window filling up.

The first time it starts, your harness asks whether you trust the folder it runs in. That prompt is yours to answer — Nightdesk never trusts the folder on your behalf. Cancelling it costs you nothing: the next start begins cleanly rather than trying to resume a session that never got going.

File ▸ New Concierge Session… forgets the conversation and starts fresh. Restart keeps it. Either way the harness’s own memory survives, so anything Concierge wrote down is still available to the new session. If you rename the session from inside it, the new name sticks.

What it can reach

Concierge’s tools are Nightdesk’s and nothing else. Whatever MCP servers you have configured for your own sessions, Concierge does not inherit them — its tool surface is exactly the Nightdesk bridge, so what it is able to do is bounded by what Nightdesk itself offers.

It can, though, see more of a launch than the rail shows. Ask it about a session you cannot find and it can tell you whether the launch ever registered, whether a terminal for it is still running, and where that terminal is — including a Codex thread being held open in the background. A session that has dropped off the rail is a question Concierge can actually answer.

Selecting it clears the rail

Concierge is not one of your agents, and selecting it says so: the rail’s own selection clears, and the two surfaces that follow the selection widen to the whole fleet. The project drawer shows the activity feed for everything at once, and the Usage tab covers the whole fleet rather than one agent and the subagents it started.

One consequence runs the other way: the menu bar’s two lists, Needs attention and Working, leave Concierge out. Its banners still work — a notification from Concierge takes you to Concierge’s pane.

When it shows you something

Concierge, like any agent, can put an image or a page in front of you, and it arrives as a tab beside its own session. When an agent shows you something covers where those land and what gets refused.