PacketChatDocs

Use chats, projects, prompts, and knowledge#

PacketChat keeps conversations, reusable prompts, project records, and ingested documents in one shared installation. Use each surface for the job it currently performs rather than treating every field as automatic model context.

Before you start#

  • Sign in to an active account.
  • Confirm an administrator has enabled at least one provider model.
  • Ask the administrator which projects and knowledge bases are appropriate for the material you will upload.

Start and continue a chat#

  1. Open Chat.
  2. Select a provider model.
  3. Enter the message and send it.
  4. Wait for the streamed response to finish before reloading or navigating away.
  5. Reopen the conversation from the sidebar to continue it.

Conversation history persists on the server. Model parameters or context shown elsewhere in the interface should be verified in the actual request behaviour before relying on them for a controlled workflow.

Organise projects and prompts#

Projects provide shared records for grouping work. Prompts provide reusable, versioned text. Create narrowly named entries, keep sensitive content out of titles, and describe the intended audience in the body.

Selecting or editing a project does not automatically prove that its instruction field entered a model request. Put required instructions into the actual chat or published agent until the calling workflow explicitly supports project context.

Add knowledge#

  1. Open Knowledge and choose or create a knowledge base.
  2. Upload a supported document within the configured size limit.
  3. Wait for the document status to reach ready.
  4. Search for a phrase that appears only in the uploaded content.

Upload readiness proves ingestion and search. It does not automatically attach the knowledge base to ordinary chat. Bind knowledge to a published agent when that agent should retrieve it.

Verify#

  • A chat response persists after reload.
  • A prompt can be reopened and its current version is visible.
  • Project membership and ownership match the intended users.
  • The knowledge document reaches ready and returns a known search result.

If it does not work#

Symptom Action
Send is rejected Re-select an enabled model and ask an administrator to test its account.
Conversation is absent after reload Confirm the response completed and the database is healthy.
Document stays queued Confirm the worker and Redis are running.
Document fails Check worker logs, object storage, file type, and upload limit.
Knowledge search works but chat ignores it Use an agent with the knowledge base explicitly bound.