Atomek

Atomek is the standalone Tytus app that provides the Tytus Resource Fabric cockpit: mission folders, shared folders, OpenClaw/Hermes pods, local AI CLIs, local files, Monaco editing, chat, artifacts, embedded docs/skills, app skills, and approval-gated outputs.

Current published app release: v0.4.35.

What it does

• Opens local files and folders through the browser File System Access API.
• Renders a VS Code-like Explorer with collapsible folders and editable tabs.
• Edits text/code/markdown in Monaco.
• Shows markdown preview and rich chat/artifact output.
• Lets chat attach active file/open editor context.
• Routes AI through the Tytus host AI bridge and global AIL settings.
• Discovers OpenClaw/Hermes pods, shared folders, local tools, AIL routes, and app skills through the Tytus host bridge.
• Creates mission folders as the shared context layer between local agents, Tytus pods, and local apps.
• Generates team presets (Repo Repair, OpenClaw + Local, Creative Production, Research Watch) from the live resource graph.
• Writes mission run/proposal/output/approval folders so every agent handoff is visible and resumable.
• Sends selected tasks to OpenClaw/Hermes pod agents through host.daemon.chatAgent() so the host preserves route identity and uses the correct Cortex/direct-agent bridge.
• Converts generated edits into artifacts or preview diffs before files are saved.

Boundary

Atomek is product surface. TytusOS is platform/runtime.

Normal Atomek development happens here, not in the TytusOS core repo. TytusOS should load Atomek from the catalog or pinned app manifest.

Hard rules:

• Do not hardcode provider model IDs in Atomek. Use host/global AIL model discovery.
• Do not direct-fetch remote pod/model endpoints from the browser. Use the Tytus host bridge.
• Do not turn Atomek into a second local-agent runtime. Control existing tray/local resources.
• Keep OpenClaw and Hermes as first-class user-facing brands; do not leak internal pod identifiers into UI copy.
• Do not write AI edits blindly. Return artifacts or preview patches first.
• Do not modify JULI3TA internals while fixing Atomek.

Branding

Atomek uses the local brand kit from /Users/sebastian/Projects/makakoo/files/atomek-brand-kit:

• tytus-app.json.icon is atomek:mark, matching JULI3TA's juli3ta:mark branded icon resolver.
• The workbench loads the Atomek mark/wordmark from bundled app assets for the Agent Team landing surface.
• CSS tokens follow the kit: bone on void, acid as the single primary accent, Space Grotesk UI, Archivo Black headlines, JetBrains Mono labels.

Development

npm install
npm run typecheck
npm run build
npm run release:check

npm run build runs Vite and then injects CSS into dist/index.js. CSS injection is required because TytusOS loads app entries by dynamic import and does not automatically pull Vite's extracted CSS file.

Tytus app entry

tytus-app.json points to the tagged CDN build:

https://cdn.jsdelivr.net/gh/traylinx/tytus-app-atomek@v0.4.35/dist/index.js

The catalog should point to the matching immutable manifest tag:

https://cdn.jsdelivr.net/gh/traylinx/tytus-app-atomek@v0.4.35/tytus-app.json

Release loop

1. Make changes in this repo.
2. Bump package.json and tytus-app.json to the same version.
3. Point tytus-app.json.entry.url at the immutable tag for that version.
4. Run:

   npm run typecheck
   npm run build
   npm run release:check
   git add .
   git commit -m "feat: ..."
   git tag v<version>
   git push origin main --tags

5. Update tytus-app-catalog/featured.json to point Atomek at the new manifest tag.
6. If TytusOS vendors or pins the catalog, update that repo and the tray dist too.

User manual

The primary user manual lives in TytusOS:

services/tytus-os/docs/user-manual/atomek.md

Whenever Atomek behavior changes, update that manual and regenerate services/tytus-cli/os-docs.md.