README

semitexa/os

An intent-first shell for a Semitexa application: you say what you want, the assistant plans it over the registered skills (#[AsAiSkill] from semitexa/llm), runs it, and shows the result; apps open as dialog windows on demand. The planner runs on semitexa/llm, so an LLM backend must be configured.

Install

Not included by the installer. Add it to an existing project from the project root:

docker compose run --rm --no-deps --user "$(id -u):$(id -g)" app composer require semitexa/os
bin/semitexa server:restart
bin/semitexa orm:sync

Composer also installs semitexa/weave and semitexa/platform-user. In web mode the shell requires a sign-in by default; create an account with bin/semitexa user:add --email=… --role=owner.

Who opens what, once sign-in is on:

An owner opens everything, on every site.
A site's admin opens the console on that site only, except the install's own apps: Terminal, Updates and Queues (and their skills) are an owner's. Prompts stay open to them: prompt overrides are kept per site.
A site's editor opens the chat, Notes, Calendar, Settings and the CMS on that site, and does not add or open web apps. Each person's launcher, chat suggestions and leisure chips list only the windows they can open.
A user of another site is shown the sign-in form.
Every account changes its own password in Settings. One whose password an operator set (user:password --must-change) opens nothing else until it does.

A desktop install (SEMITEXA_WINDOW_MODE=os) asks for no sign-in unless SEMITEXA_OS_AUTH=1: the person at the machine opens the console and every route that asks for a sign-in. Only a request from this machine counts as them — a loopback address, or one SEMITEXA_OS_DESKTOP_CLIENTS lists (addresses or CIDR blocks, comma-separated): with the app in a container, the desktop's own browser arrives from the container network's gateway, which goes there. Any other client is asked to sign in, and the log says so once. A web install always asks; SEMITEXA_OS_AUTH=0 is ignored there, with a warning in the log.

Calendar events the assistant made before 2026-10-27 have no owner, and Calendar shows a person only their own. On a desktop install with sign-in off, bin/semitexa update hands them to the person at the machine (data patch semitexa/os:claim-desktop-calendar); anywhere else nothing tells whose they were, and they stay unowned.

What it provides

The shell at /os and sign-in at /os/login (sign-out /os/login/out); the paths are configurable with SEMITEXA_OS_SHELL_PATH, SEMITEXA_OS_LOGIN_PATH and SEMITEXA_OS_LOGOUT_PATH.
Built-in apps, each an assistant skill that opens a dialog: Calendar, Notes, Terminal, Prompts (browse and override the prompt catalog), Settings, Updates.
Assistant skills for the environment itself, among them design-skin / reset-skin, set-theme-mode, set-locale, rename-assistant, add-input-layout / remove-input-layout, remember / recall, attach-folder, calendar-create, os:status, os:updates.
A conversation history and a knowledge graph woven from it into semitexa/weave (a background timer; OS_WEAVER=off disables it).
Tables os_conversation_turn, os_conversation_summary, os_process.
Console commands: os:design-skin, os:reset-skin, os:weave.
Settings: SEMITEXA_WINDOW_MODE (web, the default, or os), SEMITEXA_OS_AUTH (1 turns sign-in on for a desktop install, 0 off; a web install always asks), SEMITEXA_OS_DESKTOP_CLIENTS (addresses besides loopback treated as the desktop's own browser), SEMITEXA_OS_LOCALE.
resources/os-desktop/: the optional native pieces for running the shell as a Linux desktop (window manager, local bridge, X session). See its README.

More apps ship as separate packages: semitexa/files, semitexa/music, semitexa/tasks, semitexa/tictactoe, semitexa/webapps, semitexa/cms.

Documentation

Commands: https://semitexa.com/docs/reference/commands-os

License

MIT, see LICENSE.

semitexa / os

Package info

Security

Fund package maintenance!

Statistics

README

Install

What it provides

Documentation

License