Skip to main content

Celeris on your phone

Celeris for Android does two things: chat with celeris-1 directly, and run tasks on a computer you are signed in on. Sign in with the same Celeris account as your desktop.

Chat​

Start a chat and type a question. Follow up in the same conversation, or start a new chat for a new topic. To add context, share text or an image into Celeris from another app; review it before you send. Earlier chats stay in your history.

Run work on your computer​

The work, the files, the sign-ins and the tools you configured usually live on your computer. A remote session lets you type the task on your phone while the computer does the work, streaming each step back to you.

  • Your phone chooses the task, shows the transcript as it arrives, answers approval prompts, and can stop the run.
  • Your computer does everything else: it picks the tools, runs the commands with its own files, sign-ins and working folder, and keeps the history.

Nothing runs on the phone, so it never needs your git credentials or connector tokens.

Setting it up​

  1. On the computer, open Settings → Remote, turn on remote sessions, and give it a name you will recognise under This device's name.
  2. On the phone, turn on remote sessions in Settings → Remote.

Then pick the computer in the Run on picker and type the task. Follow-ups stay on the same computer. A computer that is asleep or offline stays in the picker, marked offline, until it is back.

Both apps must be on compatible versions. A device that is behind shows in the picker but will not take work until it is updated.

Approvals​

Approval prompts appear on your phone, but the computer's rules decide what needs one. Reads run, writes ask, and anything that cannot be undone or leaves the machine asks every time, exactly as in Approvals & safety. Stop on the phone stops the run on the computer.

The phone and computer connect through a relay that passes your task, the transcript and your approval answers. It does not hold your credentials, and files and command output are not shared beyond what the transcript shows.