From a first draft to a coordinated team, start with the work you want to do. Choose a THOX device, use ThoxOS, and connect only the resources you authorize through MeshStack. ThoxWork will bring people and agents together when available.
ThoxOS desktop capture · Explore the recorded interfaces and labeled previews below.
From device to workspace
The same four-step path underlies every workflow below: choose a device, run ThoxOS, optionally join MeshStack, and eventually organize the work in ThoxWork.
1
Choose a THOX device
Campaign family
ThoxKey, ThoxAir, ThoxMini, and ThoxClip each bring a different way to carry, connect, or keep your work close.
The upcoming workspace for people, Digital Employees, projects, approvals, and shared work. Available previews remain separate from a provisioned workspace.
Twelve workflow ideas, from your first draft to your next team project. Choose a category, then explore the steps, the outcome, and what the experience needs.
Selected workflow: Turn a long document into a useful brief
12 workflows
Everyday workWorkflow example
Turn a long document into a useful brief
Get oriented before a conversation, without losing sight of the source.
Input
Text from your own document, or a file type your installed client supports.
Devices & apps
ThoxKey · ThoxMini · ThoxOS · ThoxBeam within ThoxOS on ThoxKey
Steps
1
Choose the material
Bring in only the sections needed for the task and select a compatible local model.
2
Ask a focused question
Request the main points, unresolved questions, and passages worth checking.
3
Check and keep
Compare the draft with the original, correct it, and save your own final brief.
Outcome
A concise brief, a question list, and a clearer starting point for your own judgment.
Local document support and model fit depend on the client and release. ThoxKey uses a compatible host computer.
Explore recorded desktop interfaces and clearly labeled mobile and desktop design previews. Nothing here is live device telemetry.
Recorded interface views from ThoxOS and MeshStack. These show selected builds, not a live connection to your devices.
ThoxOS v1.5.1 desktop capture on Windows. Recorded interface view.Desktop capture
What is shown (silent media)
The Home surface shows the main navigation, model and device status cards, recent work, and setup. This page plays media; it does not connect to or operate the recorded device.
Find the device that fits your day
Four ways into the ThoxOS experience. Choose by how you work; check each device page for current availability and supported capabilities.
Drive-Resident AI Runtime
ThoxKey™
The drive you carry between machines
Carry your ThoxOS workspace and its ThoxBeam runtime to a compatible computer you trust. The connected host supplies execution.
A wireless companion for light local functions and permitted mesh work as you move between tasks. Choose the supported client and resource path for your release.
Every workflow above runs in one of these three modes. They are separate paths you choose between, not a stack that silently falls back from one to the next.
Local: a compatible device or host
Choose a qualified local runtime and model to process the task on hardware you control. ThoxKey uses its connected host for execution.
Prepare required assets before going offline. Input support, model fit, and available functions vary by client and release.
Mesh: resources you authorize
Use MeshStack to connect authenticated devices and compute, then select a permitted capability for a supported workflow.
Device enrollment, data access, and action permissions are separate. Discovery alone does not promise distributed inference or a performance gain.
Hosted: an explicit online choice
Try the browser demos and available hosted app previews before choosing hardware. A hosted path uses online infrastructure.
Use sample or non-sensitive inputs. A hosted demo is not evidence of offline execution, and local workflows must not silently switch to cloud processing.
Frequently asked questions
No. These are workflow ideas, not a universal feature checklist. The device, client, model, runtime, and release determine which steps are supported. ThoxAir and ThoxClip are companion devices; a workflow may need a compatible host or an explicitly connected resource.
Local execution requires a compatible runtime, a model that fits, and the necessary assets already available. Setup or connected services may require internet access. Supported local-network mesh workflows still need their network; hosted demos require an online connection.
MeshStack connects authenticated devices and compute into a distributed private AI mesh. You choose which supported resources a task may use. Joining the mesh does not automatically grant access to all files, replicate memory, combine device memory, or enable every distributed workload.
ThoxBeam is the portable AI runtime engineered for ThoxKey within ThoxOS. It is not a separate platform. The connected host supplies execution, so use a computer you trust; carrying the runtime on a drive does not protect you from a compromised host.
No. The gallery contains recorded desktop interface views and clearly labeled design previews. The MeshStack desktop showcase pans across a captured screen, rather than demonstrating an interaction. Recordings do not verify every device, model, or connection shown by an interface.
ThoxWork is the coming-soon human-and-agent workspace. ThoxEmployee provides Digital Employee runtime and lifecycle tooling. Rolodex powered by THOXY™ helps you discover roles and introductions. Exploring a role or exporting a profile does not activate an employee, connect accounts, or provision ThoxWork.
Choose one small task and use non-sensitive sample text in the hosted demo. Then check the relevant device and platform pages for the experience you want. Follow the Kickstarter page for current campaign information; these examples do not change product availability or delivery commitments.
Bring these workflows to your own work
Explore the full workflow list above, try the hosted demo in your browser, or follow the THOX campaign for the four-device lineup.
