Oxy's assistant: it acts for you in your Oxy apps and works in the background. Your own agents, the gemies, live in Gemies.
The Alia app (web, iOS, Android), built on @gemies/sdk.
Important
The backend lives in OxyHQ/Gemies since 2026-11-12:
the API behind api.gemies.ai, the integrations service, the agents' computer host, the SDK
(@gemies/sdk) and the server client (@gemies/server), their deploys, releases, canaries,
runbooks and architecture decision records
(ADR 0034).
Backend changes go there, not here.
One workspace.
| Path | Package | Stack | Purpose |
|---|---|---|---|
packages/app |
@alia/app |
Expo 58 | The Alia app: alia.onl, iOS and Android |
The conversation, voice and runtime come from @gemies/sdk,
installed from npm. It replaced @gemies/sdk and @gemies/server, which were published from
here until 2026-11-12 (Gemies ADR 0034 §6).
Identity comes from the Oxy platform rather than from a login system here:
@oxy.so/services and @oxy.so/core, with @oxy.so/bloom
for shared UI. See docs/oxyhq-auth.md.
Important
Alia has no models of its own. A person picks a power level (auto … ultra) and
Oxy picks the model. No client names a model: with nothing chosen a request carries no
model and the server's default answers (scripts/check-model-defaults.mjs). Model and
publisher names are shown; the operator serving a deployment and deployment IDs stay off
the product surface.
The bun version is pinned in packageManager and CI installs that exact version.
bun install
cp packages/app/.env.example packages/app/.env # EXPO_PUBLIC_API_URL points at the API
bun run dev:app # Expo (web + tunnel)
The app has platform shortcuts at the root:
bun run web # or ios, or android
| Group | Scripts |
|---|---|
| Build | bun run build:app |
| Start | bun run start:app |
| Lint / format (Biome) | bun run lint (check), bun run lint:fix, bun run format |
Warning
Bumping an Expo SDK version touches three files, not one. The root package.json
carries an overrides block that pins Expo packages tree wide, and those pins beat
whatever packages/app/package.json declares. That is why bunx expo install --fix
loops forever: the override resets the version it just wrote. A correct bump edits
packages/app/package.json, the root overrides block, and bun.lock.
| Doc | Subject |
|---|---|
| Overview | What lives here, what lives in Gemies, and the reading order |
| App architecture | The feature tree and its import rules |
| Embedding a gemie | The SDK's wire contract (in OxyHQ/Gemies) |
| Instant loading | Skeletons instead of spinners |
| Bloom adoption | The Alia → Bloom map |
| Native validation | Checking the app on a device |
| Oxy auth | Identity and sessions |
| Dependency updates | Reviewable Oxy updates and Doctor |
| Gemies docs | The backend: chat runtime, models, voice, agents, API reference, deployment |
Read CONTRIBUTING.md first. Three rules are worth repeating, because each is easy to break by accident and none is caught by types:
- Never expose the operator serving a model (Groq, Cerebras, OpenRouter…) or a deployment ID on the product surface — the UI, errors, customer-facing analytics. Model and publisher names are fine.
- The conversation screen is the SDK's (
GemieChatContentin@gemies/sdk); the app supplies only its own chrome through props and slots. - No model id in code or environment, and no curated model list.