PacketChatDocs

Use agents and approvals#

PacketChat agents package instructions, a model selection, permissions, and knowledge bindings into a reusable published version. Runs always use the published version, so editing a draft does not change existing behaviour until it is published again.

Before you start#

  • Confirm the required provider model is enabled.
  • Prepare the instruction text and any knowledge base the run may search.
  • Decide which actions require explicit approval.
  • Use a test account and non-production endpoints for the first run.

Build and publish an agent#

  1. Open Agents and create a draft.
  2. Give it a specific purpose and instructions.
  3. Select the provider account and model.
  4. Bind only the knowledge bases and actions it needs.
  5. Configure the step and action budget.
  6. Publish the draft.

Publishing creates the version used by later runs. When changing behaviour, publish a new version and run the same acceptance prompt before wider use.

Run the agent#

  1. Open the published agent.
  2. Start a run with a narrow request.
  3. Review the run timeline and any retrieved knowledge.
  4. If an action requests approval, inspect its destination and arguments before deciding.
  5. Read the final run status and stored output.

The current approval path executes an approved action but does not continue model generation afterward. Treat the action result and run status as the end of that run, then start a follow-up run if interpretation is required.

Code interpreter and runtime MCP actions are not available in the current release even if their controls appear in the builder.

Verify#

  • The run records the intended published version.
  • The selected model account and owner are correct.
  • Bound knowledge produces a known retrieval result.
  • Disallowed actions cannot run without approval.
  • An approved test action reaches only the expected endpoint.

If it does not work#

Symptom Action
Draft edits have no effect Publish the draft and start a new run.
Run cannot use a model Confirm the provider account is active and the model binding is enabled.
Knowledge is absent Bind the knowledge base to the draft, republish, and wait for documents to be ready.
Run stops after an approved action Start a follow-up run with the action result; automatic continuation is not available.
An action target is refused Use an allowed HTTPS endpoint and review the installation network policy.