Skip to content

TytusOS, Private Pods, and Tytus Apps

TytusOS is the local browser desktop that comes with Tytus. It gives each user a practical control surface for a private AI pod: files, terminal, chat, shared folders, agent apps, settings, and pod inspection. The web app at https://traylinx.com/admin/tytus is the account-side control center. The local desktop runs at http://localhost:4242 after Tytus is installed.

Use this page as the canonical user-facing Tytus guide.

Surface URL Use it for
Public tytusOS landing https://tytus-os.traylinx.com/ Product explanation, pricing, app overview, marketing
Installer page https://get.traylinx.com/#install Current macOS, Linux, and Windows install commands
Traylinx Tytus page /admin/tytus Subscription state, installers, WireGuard config, env block, app links
Local tytusOS desktop http://localhost:4242 Files, Terminal, Chat, Settings, apps, Pod Inspector
OpenClaw https://openclaw.traylinx.com/ Coding, scripts, local repo work, shared-folder missions
Hermes https://hermes.traylinx.com/ Messenger-native personal agent, memory, scheduled work

If a user types “titles”, “titus”, or “Tytus OS”, treat it as Tytus / tytusOS.

What Tytus includes

Tytus is the private AI pod product. A subscription gives the user one or more pod units. Each pod is isolated, WireGuard-tunneled, and exposes an OpenAI-compatible AIL gateway so common AI tools can use the same private endpoint and key.

The stack has four layers:

  1. Traylinx account: subscription, billing, dashboard, /admin/tytus, and assistant.
  2. Tytus CLI / tray app: installs locally, authenticates the user, starts the tunnel, manages setup.
  3. TytusOS desktop: local browser UI at http://localhost:4242 for Files, Terminal, Chat, Settings, Pod Inspector, and apps.
  4. Private pod runtime: AIL gateway, WireGuard tunnel, app runtimes, shared folders, agents.

The Tytus admin page

/admin/tytus is the canonical control surface for the private pod product. The page is the default landing for any account with an active Tytus subscription, and it auto-loads on phones for those accounts (see Mobile behavior).

Top of the page:

Anchor What's there
#install Install hero with the platform-specific one-liner for macOS, Linux, and Windows. Includes a "Tytus OS docs" tab with the local-desktop reference.
#pods Pod inventory — every pod you own with its agent, plan badge, custom name, status, and quick actions (chat, configs, deploy).

The page also surfaces:

  • Available agents — OpenClaw, Hermes, Atomek, JULI3TA cards with plan requirements.
  • Channels — links into the relevant Discord, Telegram, and email channels for support.
  • Configs & references — env block generator (OPENAI_BASE_URL / OPENAI_API_KEY), WireGuard config, and link to tytus llm-docs.
  • Cloud shared folders — see Shared folders.
  • Deploy progress dialog — when you provision a new pod or swap agents, a modal streams progress so you can watch the deploy land.

If the dashboard widgets look slightly different from this guide, the redesign sprint (REACT_APP_TYTUS_V2) may be gating some layouts behind a flag during rollout.

Install Tytus

macOS and Linux

curl -fsSL https://get.traylinx.com/install.sh | bash

Then run:

tytus setup

Windows

Use the one-line PowerShell installer:

powershell -c "irm https://get.traylinx.com/install.ps1 | iex"

Windows is public beta. The zip download is only a fallback when a browser, security policy, or shell blocks the one-liner.

First launch

After installing:

tytus setup
tytus tray install

Then open:

http://localhost:4242

You can also use Tytus without keeping the local desktop open. The CLI, tunnel, and AIL gateway keep working after setup.

Plans and pod units

Plan Monthly positioning Pod units Includes
Free Learn and browse 0 Traylinx account, shared platform assistant, no private pod
Explorer First private pod 1 OpenClaw, private AIL gateway, bundled token plan
Creator Builder plan 2 OpenClaw + Hermes, more token capacity, first marketplace listing
Operator Power user / team 4 OpenClaw + Hermes, more projects, more listings, larger token bundle

Annual billing normally saves two months. Always trust the live billing page for exact current prices, taxes, discounts, and checkout state.

Custom pod names

Every pod you provision can be renamed. From /admin/tytus → #pods, click the pod's name and type a new label (e.g. "Lisa", "Build-bot", "Hermes-personal"). The custom name appears everywhere — inventory rows, chat target selector, shared-folder attachment list — without affecting the underlying pod ID or WireGuard config.

Apps in tytusOS

Core desktop apps

  • Files: browse local and shared folders, inspect outputs, move assets between workflows.
  • Terminal: run pod-local or local-agent commands from the desktop shell.
  • Chat: talk to the private AIL gateway and pod tools.
  • Settings: account, app preferences, background, updates, privacy, daemon state.
  • Pod Inspector: check tunnel state, pod health, endpoints, ports, and allocation.
  • Agent Team / Atomek: coordinate local agents, missions, shared folders, app outputs, and approvals.

First-party apps and agents

  • OpenClaw: coding, repo repair, scripts, terminal work, long-running missions, shared-folder workflows. Available on Explorer and above.
  • Hermes: personal messenger agent with memory, skills, scheduled work, and channel workflows. Available on Creator and above.
  • Atomek: desktop mission control for local agents, files, terminal sessions, chats, and app state.
  • JULI3TA: creative music app for local and pod-assisted song workflows.
  • switchAILocal / AIL gateway: OpenAI-compatible routing layer for local and private pod models.

AIL gateway and external tools

The AIL gateway is OpenAI-compatible. Use it with Cursor, Claude Code, OpenCode, Gemini, scripts, notebooks, or any client that accepts an OpenAI-style base URL and API key.

  1. Open Traylinx → Tytus → Configs & references.
  2. Generate the env block.
  3. Copy the base URL, API key, and model aliases into your external tool.
  4. Keep the WireGuard tunnel connected for private pod routes.
  5. Run tytus llm-docs locally for the CLI-facing reference.

If a tool cannot connect, test locally:

tytus status
tytus test

Shared folders

Shared folders let web, pods, agents, and local desktop apps work on the same mission folder without copy/paste handoffs. There are two modes.

Cloud shared folders from Traylinx web/mobile

Use this when the user does not want to install TytusOS yet, or is on mobile.

  1. Open Traylinx → Tytus → Cloud shared folders.
  2. Click Create folder, give it a name, optionally pick a project to associate it with.
  3. The folder appears in the list with an "Attach" action.
  4. Select a pod from your inventory and click Attach. The pod now sees the folder at /app/workspace/shared/<folder>/inbox and /app/workspace/shared/<folder>/out.
  5. Add inputs in any of three ways:
  6. Upload from browser — drag files into the folder dialog.
  7. Add Project Assets — click Add to folder and pick existing project assets; bytes move server-side into inbox/ (the browser only requests the copy).
  8. Refresh on pod — pulls the latest inbox state onto the pod without restarting it.
  9. As agents write into out/, each output file gets a Promote action — promoting copies the output back into the originating project's asset library so it shows up in the Asset Browser.

The browser creates and manages cloud folders. It does not background-sync arbitrary local computer folders.

If the UI shows a yellow "Cloud Shared Folders backend is not deployed yet" banner, the interface is ready but the registry endpoint is still rolling out — try again in a day or use the local-binding workflow below in the meantime.

Local binding from tytusOS

After installing TytusOS, bind the same cloud shared folder to a local computer folder. This upgrades the workflow from web-only to web + pod + local filesystem.

tytus folder bind ~/Projects/my-work --name my-work

Then open tytusOS and use Files or Agent Team to select that folder for a mission. Windows shared-folder support is public beta and depends on the current installer build.

Typical uses:

  • Give OpenClaw a repo, sprint folder, or uploaded brief.
  • Let Hermes read/write approved outputs.
  • Move JULI3TA exports into a project folder.
  • Share Atomek mission folders with terminal and chat tools.
  • Sync a folder to a pod-backed or bucket-backed workspace.

Chat with your Tytus agents from the web

You don't need TytusOS or a terminal to talk to a Tytus agent — the web app can stream chat directly to any agent on any of your pods.

  1. Open /admin/tytus → #pods.
  2. Click the Chat action on any pod row (e.g. OpenClaw on Pod 01, Hermes on Pod 02).
  3. The Personal Assistant opens with that pod + agent pre-selected as the chat target.
  4. The target selector at the top of the chat lets you switch between:
  5. Platform — shared Traylinx assistant (free tier-style).
  6. Tytus Brain — your default pod's primary agent.
  7. Specific agent on a specific pod — e.g. "Lisa · OpenClaw".
  8. Messages stream token-by-token. The response shows the active source (which agent on which pod served the reply) so you can verify routing.

The chat picks up any shared folders attached to the selected pod, so the agent can read files from inbox/ and write to out/ without leaving the browser.

Mobile behavior

On phones and tablets, the dashboard auto-redirects to /admin/tytus for any subscribed account. The page is laid out for one-thumb operation:

  • Install hero collapses to a single platform card based on the device.
  • Pod inventory stacks vertically with the chat action prominent.
  • Cloud shared folder dialog opens full-screen.
  • The bottom-nav surfaces the most-used Tytus actions (chat, folders, deploy).

Some advanced controls (env block generator, WireGuard config download) link out to the desktop view; tap Open on desktop to send a one-tap email/QR handoff.

Common workflows

Use Tytus from web/mobile without local install

  1. Sign in to https://traylinx.com.
  2. Subscribe to Explorer, Creator, or Operator.
  3. Open /admin/tytus.
  4. Create an AIL pod or start an OpenClaw/Hermes pod.
  5. Use the web chat test or copy env/settings for OpenAI-compatible clients.
  6. Create a cloud shared folder when you need file handoff.
  7. Install local TytusOS later only when you want Files, Terminal, local folder binding, or desktop app control.

Install and connect on a new Mac

  1. Sign in to https://traylinx.com.
  2. Open /admin/tytus.
  3. Run curl -fsSL https://get.traylinx.com/install.sh | bash.
  4. Run tytus setup and sign in.
  5. Open http://localhost:4242.
  6. Generate the env block in Traylinx.
  7. Test an external tool through the AIL gateway.

Use OpenClaw on your own pod

  1. Subscribe to Explorer or higher.
  2. Install Tytus and connect the pod.
  3. Open https://openclaw.traylinx.com/ or the OpenClaw card from /admin/tytus.
  4. Point OpenClaw at a shared folder or repo.
  5. Let it run code, terminal, or repair missions on your infrastructure.

Use Hermes

  1. Subscribe to Creator or higher.
  2. Install Tytus and connect the pod.
  3. Open https://hermes.traylinx.com/ or the Hermes card from /admin/tytus.
  4. Connect channels when supported.
  5. Use Hermes for memory-backed personal workflows and scheduled work.

Use Atomek and JULI3TA

  1. Open tytusOS at http://localhost:4242.
  2. Launch Atomek from the dock for agent missions and local app control.
  3. Launch JULI3TA for music creation workflows.
  4. Save outputs into Files or a shared folder.

Troubleshooting

Problem Fix
The dashboard says no pod is allocated Confirm the subscription is active, then run tytus setup again.
Browser cannot open tytusOS Confirm the daemon is running, then open http://localhost:4242.
External tool cannot use the AIL gateway Regenerate the env block, verify the base URL/key, run tytus test.
Windows installer is confusing Use the PowerShell one-liner first. Zip is fallback.
User asks about “titles” Correct silently to Tytus and answer with current Tytus install steps.
WireGuard fails Re-run tytus setup, check local VPN permissions, then regenerate config from /admin/tytus if needed.
App looks stale after release Use the Tytus update button or reinstall from https://get.traylinx.com/#install.
Cloud Shared Folders shows "backend pending" The UI shipped ahead of the registry endpoint; retry in a day or use local tytus folder bind for now.
Pod chat reply shows the wrong agent Use the chat target selector at the top of the Personal Assistant to pin the pod + agent explicitly.
Promote button on a shared-folder output is greyed out The pod hasn't finished writing the file. Refresh the folder and try again after the file appears in out/.

Mirrored from traylinx-web:docs/user-manuals/05_tytus_os.md. Edit the source in the traylinx-web repo — changes here are overwritten by the sync script.