Choose the right workspace
ThoxWork remains Coming Soon on the public website. The live ThoxEmployee guest demo is available separately. Its availability is not a release of signed ThoxWork desktop clients or proof that an organization backend is configured.
The local ThoxEmployee kernel, supervised workspace, Migration Studio and ThoxWork review surface have separate stores and responsibilities. Profiles can move through reviewed files; the products do not automatically synchronize accounts or task history.
Review a profile before import or export
The profile-transfer page converts owned instructions and rehearses review in your browser, without connecting an account, opening a guest session or making an AI call. It accepts manually copied Grok instruction text, Hermes SOUL.md, Pi AGENTS.md or SYSTEM.md, other Markdown or plain text, and supported employee JSON. It does not import account archives or conversation transcripts; APPEND_SYSTEM.md is outside the current Pi adapter.
The homepage walkthrough illustrates an example transfer. Play, pause or step through it without importing anything. Inside the transfer page, the progress visual follows your current review and virtual import; changing the input requires a new review. Reduced-motion settings keep the walkthrough available one step at a time.
Download the reviewed employee JSON, then open the hosted workspace separately to import it. Browser rehearsal changes only a virtual roster. The JSON keeps source identities and provenance; a plain Markdown export loses that metadata and carries instruction text only.
The guest workspace accepts supported ThoxPack 1.0 or ThoxWork profile JSON: 1–25 employee profiles in a file no larger than 256 KiB. A profile carries source, identity, name, role and standing instructions.
Selecting a file in the hosted demo uploads it to your guest session for preview. Read the raw instructions and replacement choices before acknowledging the import. An export also requires a preview and acknowledgment.
Free-text instructions can contain private information. Remove secrets yourself; a credential check cannot reliably detect every secret. A source label is declared provenance, not proof of authorship.
- Prepare only instructions you own or are authorized to move, or export selected employee profiles. Remove memory, tools, credentials and private information before review.
- Open the file in the intended destination and review every name, role, source identity and instruction.
- Explicitly select any supported replacements; a matching display name is not permission to replace a profile.
- If the roster or file changes, create a fresh preview before confirming.
Profile review and execution are separate
A profile file does not transfer credentials, configure models, attach tools, grant permissions or start work. Importing a profile does not register an employee with an organization backend.
The current ThoxWork development integration includes Review pack on the Employees screen. Its authenticated server preview is read-only: there is no apply action or automatic backend registration. A remote server receives the submitted profile text, so check its destination before uploading.
Migration Studio uses a different package format and a separate operator registration process. Renaming a file does not convert its contract. Follow the matching module documentation and review any explicit conversion.
If a profile is rejected
Check the file format, version, profile count and size against the destination guide. Use an actual JSON export, not a ZIP archive, file path or URL.
For an expired or stale preview, select the file again and inspect the new preview. For an identity conflict, review the source and ID instead of changing names to force an import.
Send support the format name, module version and sanitized error message. Do not attach an unreviewed profile or a file containing credentials.