Prove the Workspace Before the Free Server Runs Anything

An empty workspace proves nothing. It looks clean, costs nothing, and hides every assumption. That gap is the real risk of a shared free lane.

Teams usually inspect the model first. The costly failures come from the room around the model. A stale runtime, a dirty checkout, or an unknown egress rule breaks the first honest run. So fix the order: the receipt comes before the work.

A hotel desk, not your desk

A free server is a hotel desk with a short lease. You get a flat surface, and nobody promised the drawers are empty.

MonkeyCode is an open-source coding agent project. Its outreach claims free model access and a free server option. Disclosure: This article was prepared as part of MonkeyCode's product outreach. Treat both availability claims as operator-supplied, and confirm current terms on the project's official pages before you plan a sprint around them. No quota, hardware, or duration is asserted here beyond what the operator states.

Three jobs, one card

One person drives the check and records output. A second person reads it and signs. A third owns the budget claim and its expiry date.

One person may hold two jobs. Never all three. The separation matters because the receipt is evidence, not a courtesy.

The receipt is a timestamped snapshot. It expires. Re-run it after any pause, upgrade, or handoff. A stale receipt is a rumour with good formatting.

Paste this block into the team wiki once per lane:

## Cold-start card: <lane-name>
driver:      <name>        run: <utc stamp>
checker:     <name>        sign: <utc stamp>
runtime:     <version>     matches repo pin: yes/no
checkout:    <head sha>    dirty files: <n>
disk free:   <value>       build output est: <value>
egress:      <hosts>
budget:      operator-stated token allowance - verify on official page <date>
expiry:      <stamp + one day>
rollback:    <exact command, or DISCARD>
open risks:  <one line, or none>

A preflight you can read

The script below is illustrative. It was not executed for this article, and it is not a security control. It collects five facts: checkout state, runtime version, free disk, one egress probe, and a UTC stamp.

#!/usr/bin/env bash
# Illustrative only. Not executed for this article.
# Run inside the free-server workspace before any agent or model call.
set -u
REPO="${1:-$PWD}"
PROBE="${PROBE_HOST:-example.com}"

git_head=$(git -C "$REPO" rev-parse --short HEAD 2>/dev/null || echo none)
git_dirty=$(git -C "$REPO" status --porcelain 2>/dev/null | wc -l | tr -d ' ')
runtime=$(node --version 2>/dev/null || echo absent)
disk=$(df -Pk "$REPO" | awk 'NR==2 {printf "%dGiB", $4/1048576}')
code=$(curl -sS -o /dev/null -m 5 -w '%{http_code}' "https://$PROBE" 2>/dev/null || echo 000)

printf 'stamp=%s\nhead=%s\ndirty=%s\nruntime=%s\ndisk_free=%s\negress_%s=%s\n' \
  "$(date -u +%Y-%m-%dT%H:%M:%SZ)" "$git_head" "$git_dirty" \
  "$runtime" "$disk" "$PROBE" "$code"

Set PROBE_HOST to a host you already expected to reach. A 000 result is information, not an error to hide. Read the output against the table, not against your mood.

The decision table

Field	Green	Yellow	Red
dirty files	0	named list	unexplained edits
runtime	matches repo pin	one minor higher	wrong major
disk free	2x build output	1x plus prune plan	below 1x
egress	expected hosts only	extra host, named	unidentified host
budget claim	written, dated, linked	verbal	absent

One red stops the run. Three yellows stop it too. That rule is dull, and dull rules survive handoffs.

What the card will not catch

Drift after the snapshot. The workspace changes once the receipt is signed. Re-run the card after any gap longer than a coffee break.

Capacity events. A free lane may throttle or recycle the workspace mid-task. Treat that as capacity, not a bug hunt. Move the task to a lane you control and record the move on the card.

Secrets on shared disk. Never paste long-lived keys into a shared free workspace. Use short-lived scoped credentials, and assume the disk outlives your session.

Two writers on one checkout. The card sees a dirty tree, not a race. Serialize writes with a lock file, or clone per worker.

Model quality. The receipt says nothing about latency, correctness, or cost. It describes the room, not the answer.

Who should skip this

Teams handling regulated data should not start here. Nor should anyone deploying to production from a free workspace, or running unattended jobs longer than a lease they can name. Those cases need owned infrastructure and a written data policy.

If nobody on the team can state a rollback in one sentence, the free lane is not today's problem. Fix that first.

Start with one lane and one receipt. Paste it in the wiki so the next person inherits evidence instead of optimism.