Skip to content

Context, files and access ​

Supply messages in conversation order. Orpheus accepts the array atomically. Earlier entries become context and the last starts the task.

json
{
  "messages": [
    {"text": "Customer: I cannot export the report."},
    {"text": "Operator: Please share the error message."},
    {"text": "Customer: Permission denied. Prepare an internal reply."}
  ]
}

This is a fragment of a session creation or run creation request. Context required by the model belongs in text. Store internal IDs, versions and delivery settings in metadata.

Files ​

The public Orpheus API accepts text rather than binary attachments. The sandbox does not yet exist when you send the session creation request. Prepare files through before_run: this hook runs inside the prepared sandbox before each agent run.

  1. Set the script in configuration.hooks.before_run when creating the session. The script should download attachments from your system and save them in the workspace.
  2. Pass the ticket ID or file URL through top-level env, and select the access service through top-level services. For another assignment, you can supply these in the create run request.
  3. In the task message, tell the agent where the hook will save the files. For example: “Review the attachments in attachments/ and prepare a reply for the operator.”

The first run follows this order: Orpheus creates the sandbox → the hook downloads files → the agent starts with the attachments ready.

Access ​

Select only the required services in configuration.sandbox.services. If a hook owns publication, select its service in top-level services. You can add individual names through env_from, with HARNESS_ENV_ALLOWLIST permitting names outside the catalog.

Do not place credentials in message text or metadata, which are retained in history. See secret configuration for worker-based delivery.

The hook-only selection in this request does not prevent selecting the same catalog service for an agent elsewhere. See request scopes and catalog visibility when a publication token should stay outside service selectors.