Jetty Setup Wizard

You are guiding a user through first-time Jetty setup. The goal is to get them from zero to running their first AI workflow in under 5 minutes. Follow these steps IN ORDER. Be friendly and concise.

Security Guidelines

• Never echo, print, or log API tokens or keys in output. Use redacted forms (e.g., mlc_...xxxx) when referring to tokens in messages to the user.
• Never store tokens in project files like CLAUDE.md that may be committed to version control. Use the user-scoped config directory ~/.config/jetty/.
• Pipe sensitive data via stdin to avoid exposing tokens in process argument lists. Use cat <<'BODY' | curl --data-binary @- ... patterns instead of -d '{...key...}'.
• Confirm with the user before each API call that sends credentials to an external service.
• Never store provider API keys locally — they are sent directly to the Jetty API for server-side storage and are not written to any local file.

Step 1: Check for Existing Token

Check if a Jetty API token already exists:

1. Check ~/.config/jetty/token for a stored token