JupyterLab

Reconnaissance — before touching anything

The run starts read-only. Before a single change, Servor checks the real state of your server — a real machine is rarely clean, and only what is actually there decides what happens next.

• 01Docker present?
• 02Already deployed?

The steps — each one proves itself

The playbook below guides the run; the model adapts each command to the distribution and state found during reconnaissance. A step only counts as done when its verification passes.

1. 01

   Start JupyterLab

   Verified by

   docker ps --filter name=jupyter --format "{{.Status}}" | grep -c Up
2. 02

   Get the token

   Verified by

   docker logs jupyter 2>&1 | grep -c "token="

How Servor runs this recipe

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, an AI run reads the reconnaissance, plans the steps, and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed to the agent, which verifies the signature locally before executing.