PacketChatDocs

Complete the first run#

A fresh PacketChat stack has no users, provider credentials, or enabled models. Create the first administrator promptly, then register and test a provider account before inviting other users.

Before you start#

  • Confirm /api/readyz succeeds.
  • Run the database migrations.
  • Have the BOOTSTRAP_TOKEN stored in the deployment environment available for this one setup call.
  • Prepare one administrator email address and a password meeting the configured policy.
  • Have an API key for one supported provider.

Create the first administrator#

PacketChat exposes a one-time bootstrap API rather than a browser form. Put the four values into a temporary JSON file with restrictive permissions:

{
  "bootstrapToken": "the deployment bootstrap token",
  "email": "the administrator email address",
  "password": "the administrator password",
  "displayName": "Administrator"
}

Submit it locally, then securely delete the temporary file:

curl -fsS -X POST http://localhost:3000/api/admin/bootstrap -H "Content-Type: application/json" --data-binary @bootstrap.json

The endpoint succeeds only while the user table is empty. After the first administrator exists, subsequent bootstrap requests are refused.

Sign in and add a provider#

  1. Open /login and sign in with the new account.
  2. Open Admin → Providers.
  3. Add the provider type, display name, base URL when required, and API key.
  4. Test the account.
  5. Run model discovery.

Discovery updates the model bindings for that account. Review the resulting model list before inviting users, especially when a provider returned an empty or unexpectedly short list.

Send the first chat#

  1. Open Chat.
  2. Select one of the discovered models.
  3. Send a short message.
  4. Confirm the reply streams into the conversation.
  5. Open Admin → Usage and confirm the request was recorded.

Verify#

The installation is ready for users when:

  • the administrator can sign in through the public HTTPS URL;
  • the provider account test succeeds;
  • at least one expected model appears in Chat;
  • a response streams and persists after a page reload; and
  • usage records identify the request.

If it does not work#

Result Action
Bootstrap returns forbidden Confirm the submitted token exactly matches the deployment value.
Bootstrap reports complete Use the existing administrator account; the setup endpoint cannot create another.
Provider test fails Confirm the API key, base URL, provider type, and provider-side access.
No models appear Run discovery and inspect its result before trying another chat.
Chat rejects the model Confirm the selected model remains enabled for the chosen account.

Next#