Skip to main content

Quickstart

About a minute, assuming Celeris is installed and signed in.

1. Act on what is on screen​

Put something in front of you worth acting on, such as a failing test, an email, a calendar, or a repository in a terminal. Then press:

Alt+Shift+D

That is ⌥⇧D on macOS. Celeris captures the screen and opens a single input over it. Type one line of intent and press Enter:

raise a PR for this branch

Esc dismisses the overlay without running anything.

2. Approve the first step​

Celeris decides what the screen implies and proposes the tool calls to get there. Read-only steps run straight away. Anything that changes something stops and asks.

  • Run allows this one call.
  • Deny refuses it, and you can tell Celeris why.
  • Always allow adds this shape of command to your allowlist, so it runs without asking next time.

The chat window opens and streams each step as it happens. Stop cancels the turn and kills whatever is running.

3. Follow up​

The run ends with a plain summary. Keep typing in the same session to continue. Follow-ups reuse the context, and the screenshot stays attached only to the turn that captured it.

Without a screenshot​

Open Celeris like any app, choose New chat and type the task. Same loop, no capture:

what changed on main since Friday?

Use mini mode (Alt+Shift+M) for a quick follow-up while you stay in another app.

Try these​

  • summarise this thread into three bullets I can send
  • what's failing in CI here?
  • create an issue for the error on screen
  • open the doc this links to and pull out the dates

Next​