Skip to setup
FTF STARSHIP
FLEET FIELD GUIDE · YOUR FIRST LAUNCH

Welcome aboard,
Captain.

One ship for your work. One fleet moving forward.

Starship brings your projects, tasks, daily plan and progress together. Talk to Claude to set your course, keep the crew informed and close the loop at the end of the day.

Connect Claude Read the launch guide
New crew member? Ask your Starship administrator for an invitation, then set your password. This guide is open to everyone; your work stays behind sign-in.
01 · CONNECT02 · WORK03 · STAY IN TOUCH
FLIGHT CHECK 01

Bring Claude onto the bridge

Set up once. No API key or personal token needed.

  1. Sign in to Starship and open Connections → Connect Claude.
  2. In Claude, open Customize → Connectors → + Add → Add custom connector. Name it Starship and paste this address:https://ftf-starship-production.up.railway.app/api/mcp
  3. Continue. Choose Sign in now and Register automatically if asked. Leave client ID, secret and request headers empty.
  4. Sign in to Starship when prompted. To save changes, check Allow user-approved project, task, planning, reporting and authorized Trello changes, then Allow connection. Read-only access lets Claude view your work.
  5. In your Claude chat, open + → Connectors and enable Starship.
FLIGHT CHECK 02

Set your course. Keep a flight record.

Talk naturally. Review the proposed changes before approving a save.

Morning launch
“Plan my day in Starship. Ask about in-progress work I left out. Show me the plan before saving.”
Start a work session
“I’m starting work on assessing the ION Inform state of the code.”
Switch or work in parallel
“Start the next task. Keep the first running with AI.”
Finish a session
“I finished that session. The task still needs testing.” Or explicitly ask to mark the task complete too.
Return to port
“Help me finish my day in Starship. Ask about gaps, breaks, outcomes and extra hours.”

Prefer the controls? Open My day to plan and report through the Starship UI.

FLIGHT CHECK 03

Open your Slack comms channel

Optional personal notifications, delivered as Slack DMs.

  1. In Slack, open your profile → More → Copy member ID.
  2. Open Starship Connections → Slack notifications, paste your ID and select Send verification code.
  3. Enter the six-digit code from your Slack DM and select Verify Slack.
  4. Choose weekday reminders and/or notices when your assigned work changes. Set times in Chicago time, then Save Slack preferences.

Check delivery history in Transmissions. You can disconnect Slack or Claude from Connections.

ENGINEERING DECK

Help build the ship.

Developers, testers and documentation contributors are welcome. Start with one clear improvement.

Open GitHub repository Contributor instructions

If GitHub shows a 404 or access request, sign in and ask the repository administrator for access. Starship membership does not automatically grant GitHub access.

  1. Find your assignment. Review issues or discuss a proposed change with the maintainers. Read AGENTS.md and the README before editing; stay within approved scope.
  2. Launch a local demo. Install Git, Node.js 22 LTS (22.12+) and pnpm 10.25. Use Docker Desktop for local services, or the documented PostgreSQL fallback.
Local setup commands
git clone https://github.com/From-the-Future/ftf-starship.git
cd ftf-starship
pnpm install
git switch -c codex/your-change

Copy .env.example to .env, apps/web/.env and packages/database/.env. Keep the local demo settings. No external service credentials are required.

docker compose up -d
pnpm db:generate
pnpm db:migrate
pnpm db:seed
pnpm dev

Open localhost:3000 and choose a fictional demo account. Without Docker, run pnpm db:local in a separate terminal instead of Compose and keep it running. Do not start both databases on the same port.

  1. Make a reviewable change. Keep credentials out of source and chats. Use only the local demo database for tests. Preserve organization permissions, private logs, audit records and explicit approval for work changes.
  2. Check your work. Run lint, typecheck, tests, browser tests and build. Run migration checks for database changes. Update relevant help/tutorial content, add a new audience-scoped release note for visible changes, and record actual results in IMPLEMENTATION_STATUS.md.
  3. Open a pull request. Push your branch and describe the problem, change and checks you ran. Include screenshots for visual changes. Maintainers review and handle production releases.
Validation commands
pnpm lint
pnpm typecheck
pnpm test
pnpm exec playwright install chromium
pnpm test:e2e
pnpm build
pnpm db:verify

Ship schematics: Architecture · Testing · Help & release notes