---
title: "Security"
description: "Where each credential of Skyworker is, and what never enters a workspace."
---

> Documentation Index
> Fetch the complete documentation index at: https://skyworker.system3inference.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Security

Everything runs in your Cloudflare account. No secret goes to a hosted service. The one exception is your licence key, which goes to the release server.

## Where each credential is

| Credential | Where it is | Enters a workspace |
| --- | --- | --- |
| Licence key | `~/.skyworker/license-key`, mode 600. Sent to the release server only. | No |
| Cloudflare API token | Your environment (`CLOUDFLARE_API_TOKEN`) or a file for `--token-file`. Never an argument. | No |
| Control token | `~/.skyworker/control-token`, mode 600, and the Worker secret `CONTROL_TOKEN`. | No |
| Workspace password | Derived from the control token and the workspace id. Saved in `~/.skyworker/workspaces/<id>.password`, mode 600. | The workspace gets it to protect its own server. |
| Device token | The paired device. It lasts 30 days. You can revoke it. | No |
| GitHub token | The Worker secret `GITHUB_TOKEN`. | No. See below. |
| Model keys | Worker secrets such as `ANTHROPIC_API_KEY`, if you set them. | No. See below. |
| Notify URL | The Worker secret `NOTIFY_URL`. | No |
| SSH key | `~/.skyworker/ssh/id_ed25519` on your machine. The public half goes to the workspace. | Public half only |

## Egress injection

The Worker adds a credential to an outbound request. The credential does not enter the container.

- A workspace that calls `github.com` sends a placeholder. The Worker swaps it for the GitHub token.
- A workspace that calls a model provider sends a placeholder. The Worker swaps it for the key, if you set one.
- With no key, models use the AI binding of your account. No key exists to leak.

The disk, the environment and every snapshot hold only the placeholders.

A provider that you log in to from inside a workspace is different. Its credential is written to the disk and into every snapshot after.

## What a device can reach

A paired device gets its own token. It never gets the control token or a workspace password. It can see and answer sessions, start tasks and wake workspaces. Pair it with `--no-terminal` so it cannot open a terminal. Revoke a device with `skyworker devices --revoke <id>`. See [Use Skyworker from a phone](https://skyworker.system3inference.dev/docs/guides/phone/).

## What an agent can do

Claude Code and Codex run with no permission prompts. The workspace is their sandbox. Text that an agent reads can tell it to do something you did not ask for.

- The agent runs as the user `user` in the container. This user has passwordless `sudo`, so the agent can install packages.
- By default a workspace has internet access, so it can clone and install. The setting `lockdown: true` turns general internet off. Only the provider hosts whose secret is set resolve.
- The GitHub token reaches what you gave it. Use a fine-grained token to hold an agent to a few repositories. See [GitHub access](https://skyworker.system3inference.dev/docs/guides/github-access/).
- A workspace is disposable. `skyworker delete` throws its disk away.

Review what an agent pushes. Do not put secrets on the workspace disk.

## The Worker URL

The Worker URL is on the internet. The control token protects the control API. The workspace password protects the routes of one workspace. A preview needs a one-time sign-in link, unless you made a public URL with `skyworker preview --public`. Only the control token can make or remove a public URL.

## The installer

The installer checks the SHA-256 and the Ed25519 signature of a build with a public key. A build with no valid signature is not unpacked and not run. The installer has no dependency.

Source: https://skyworker.system3inference.dev/docs/concepts/security/index.mdx
