nightjar

A workspace for background agents

Good work
keeps going.

Give Codex and Claude a task, connect the tools they need, and get on with your day. Nightjar keeps the work moving in the cloud.

Put an agent to work See it in motion

Bring your own model account. Start with a prompt.

The agents you know.
A workspace that stays with them.

Codex
Claude
Your account.
Your choice.

From a thought to something useful

Hand it off.
Keep your momentum.

Start a run from Nightjar or the assistant you’re already using. The work carries on when you close the chat.

Interactive walkthrough
YOUR REQUEST

Build a simple launch checklist I can share with my team.

ClaudeNo connections needed
Launch checklistReady to start
  1. ✓Turn the brief into a plan
  2. ✓Build and check the result
  3. ✓Save the files and summary
launch-checklist.htmlA working checklist, ready to review.

An illustrative example. No task is running and no account is connected.

A clear brief. A useful result.

Less setup.
More getting to it.

Read the quickstart
01 / CONNECT

Bring your agent.

Sign in to your own Codex or Claude account. An Environment holds the execution setup you’ll use again.

02 / DELEGATE

Say what good looks like.

Send a prompt and choose the connections the task needs. Reusable agents are there when you want them.

03 / PICK IT UP

Come back to the work.

Follow progress, answer a question, download files, or send a follow-up. Every run has a link and a history.

Bring the context along

The tools you use.
The access you choose.

Let an agent read the issue, check the numbers, or draft the next step. Pick connections for each run and choose read or write access where supported.

Explore connections
GitHubLinearPostHog
NotionSlackGmail
CalendarDriveVercel

Also connects to Railway, Supabase, and Expo.

Built to connect

One endpoint.
A lot of possibilities.

Give your assistant a way to delegate. Or build background work into your own product with the API and signed webhooks. 

{
  "mcpServers": {
    "nightjar": {
      "url": "https://app.usenightjar.com/mcp"
    }
  }
}

Use a remote MCP client with OAuth. Configuration syntax varies by client.

Connect once.
Delegate from anywhere.

Hosted MCP with OAuth and PKCE, or a scoped workspace API key. Start work, check progress, and collect the result.

Connect your assistant

Submitted to Muse for review. Directory availability is subject to Meta’s review.

Know what you’re handing over

Clear boundaries.
Visible work.

You choose the access.

Connections are selected per task. Saved service credentials stay on the server, and you can revoke client access in Nightjar.

Work has a paper trail.

Runs keep their status, activity, results, and questions together. A disconnected client doesn’t cancel a task.

Start small. Review the result.

Use Nightjar for work you can inspect. Review the result before acting on it; model and connected-service limits apply.

Read the pilot limits ↗

Something on your mind?

Give it somewhere to go.

Sign up with Google. Your own workspace, no invitation needed.

Get started