AppMana CLI & llms.txt

Use the appmana CLI and https://appmana.com/llms.txt to create an account, provision Git LFS, and build, deploy, and publish Streamed or WebGL Unity projects.

AppMana publishes machine-readable instructions and agent skills so coding agents (Claude Code, Codex, Antigravity, Cursor) and developers can automate the entire Unity-to-web lifecycle from the terminal.

llms.txt & Agent SKILL.md Downloads

Point your coding agent at /llms.txt or install the standalone SKILL.md files into .agents/skills/ or .claude/skills/:

  • /llms.txt — Complete single-file reference covering the appmana CLI, Unity 6 migration rules, camera & canvas hierarchies, PerUserGraphicRaycaster, and Input System wiring.
  • appmana-cli (SKILL.md) — Creating an account without a browser, authenticating, provisioning Git LFS, and building/deploying Streamed or WebGL projects.
  • unity-6-migration (SKILL.md) — Upgrading Unity 2021–2023 projects to Unity 6 (6000.3+) based on 20+ production migrations.
  • appmana-plugin-and-input (SKILL.md) — Setting up RemotePlayableConfiguration, camera/canvas hierarchies, PerUserGraphicRaycaster, and Input System actions.

Overview of the appmana CLI (@appmana-public/cli)

The appmana CLI drives https://appmana.com/graphql using your OAuth 2.0 Device Authorization Grant + PKCE token (clientId: "appmana-cli").

  • Configuration: ~/.config/appmana/config.yaml (endpoint, issuer, clientId, cluster, namespace, output)
  • Credentials: ~/.config/appmana/credentials.json (mode 0600, automatically refreshed within 60 seconds of access-token expiry; override with APPMANA_CREDENTIALS_FILE or APPMANA_TOKEN in CI)
  • Exit Codes:
    • 0 — Success
    • 1 — GraphQL or unexpected runtime error
    • 2 — Usage error or BAD_USER_INPUT
    • 3 — UNAUTHENTICATED (run appmana login)
    • 4 — FORBIDDEN
    • 6 — Network or endpoint unavailable

1. Creating an Account & Logging In

Browserless Account Creation (appmana account create)

Coding agents can register a new AppMana account without opening a browser. The command starts an OAuth 2.0 device authorization grant, submits Keycloak's registration form in an isolated in-memory session, approves its own device code, stores the credentials, and files a workspace access request:

umask 077 && printf '%s\n' "$PASSWORD" > ~/.config/appmana/account.password
appmana account create \
  --email dev@example.com \
  --first-name Dev \
  --last-name User \
  --password-file ~/.config/appmana/account.password \
  --accept-terms \
  --verification-link-file /tmp/appmana-verify.url

If email verification is required by the realm, write the emailed verification URL to /tmp/appmana-verify.url (or open it in a browser) while the command waits; appmana account create automatically completes verification and saves the login.

Interactive Device Login (appmana login)

If you already have an account:

appmana login
appmana whoami --remote
appmana accounts status
appmana accounts request-access

2. Installing the Plugin & Provisioning Git LFS

From the root of your Unity project (where Packages/manifest.json is located):

# 1. Add the OpenUPM scoped registry (UniTask, UniRx) and com.appmana.unity.public to Packages/manifest.json
appmana unity install . --public-only

# 2. Provision unlimited Git LFS storage on lfs.appmana.com and merge .lfsconfig into your branch
appmana lfs provision
git push

appmana lfs provision creates an LfsRepository in your workspace, waits for the operator to commit .lfsconfig to your GitHub branch through the AppMana GitHub App, and merges that commit into your local checkout so git push uploads large binary assets directly to lfs.appmana.com.


3. Building & Deploying a Streamed Project (Windows / Linux GPU)

Create three declarative YAML files (source.yaml, project.yaml, and deployment.yaml), replacing user-<sub> with the namespace shown by appmana whoami --remote:

# source.yaml
apiVersion: build.appmana.com/v1alpha1
kind: SourceCredentialBinding
metadata:
  name: my-game-source
  namespace: user-<sub>
spec:
  provider: github
  accountRef: <github-username>
  repositoryScope: https://github.com/<owner>/<repo>
# project.yaml
apiVersion: build.appmana.com/v1alpha1
kind: BuildProject
metadata:
  name: my-game
  namespace: user-<sub>
spec:
  displayName: My Game
  lfs:
    enabled: true
    unlimited: true
  source:
    provider: git
    git:
      repository: https://github.com/<owner>/<repo>
    revision: main
    credentialBindingRef:
      name: my-game-source
  targets:
    windows: true
    linux: true
    webgl: false
  unity:
    version: automatic
    projectPath: .
  runtimeDefaults:
    maxBitrate: 14000000
    maxEncodingDimension: 2048
# deployment.yaml
apiVersion: build.appmana.com/v1alpha1
kind: StreamingDeployment
metadata:
  name: my-game
  namespace: user-<sub>
spec:
  projectRef:
    name: my-game
  clusterTargetRef:
    name: appmana-cluster-03
  platforms:
    windows: true
    linux: true
  graphics:
    windows: direct3d12
    linux: vulkan
  resources:
    requested:
      cpu: "2000m"
      memory: "4000Mi"
      gpuCount: 1
      gpuMemoryMiB: 2048
  scaling:
    minReplicas: 1
    maxReplicas: 8
    idleSeconds: 300
  settings:
    targetFrameRate: 60
    maxBitrate: 14000000
    maxEncodingDimension: 2048
    useHardwareEncoder: true
    quitInsteadOfIdle: true

Run the project lifecycle commands:

# 1. Create the project, deployment, and source binding
appmana projects create \
  --build-project @project.yaml \
  --streaming-deployment @deployment.yaml \
  --source-credential-binding @source.yaml

# 2. Submit a cloud build for Windows and/or Linux
appmana projects build my-game --revision main --windows --linux --no-webgl

# 3. Monitor build progress & inspect build logs
appmana build-requests list --project my-game
appmana pipeline-runs list
appmana logs query --query '{namespace="user-<sub>-build"}' --start 2026-11-17T00:00:00Z --end 2026-11-17T23:59:59Z

# 4. List completed immutable BuildArtifacts and deploy to the StreamingDeployment
appmana build-artifacts list --project my-game -o json
appmana projects deploy my-game --artifact <artifact-name> --deployment my-game --dry-run
appmana projects deploy my-game --artifact <artifact-name> --deployment my-game

# 5. Verify rollout readiness (status.observedGeneration == metadata.generation)
appmana streaming-deployments get my-game -o json

# 6. Publish a public watch route (https://appmana.com/watch/<alias>)
appmana projects publish my-game --deployment my-game --alias my-game-live --dry-run
appmana projects publish my-game --deployment my-game --alias my-game-live
appmana artifact-aliases get my-game-live -o json

4. Building & Publishing a WebGL Project

WebGL builds use the same BuildProject resource with spec.targets.webgl: true and are promoted to public CDN delivery via ArtifactPublication:

# 1. Enable the WebGL target on your BuildProject
appmana projects patch my-game --input '{"spec":{"targets":{"webgl":true}}}'

# 2. Submit a WebGL build
appmana projects build my-game --revision main --webgl --no-windows --no-linux

# 3. Find the completed BuildArtifact containing spec.webgl.oci.digest
appmana build-artifacts list --project my-game -o json

# 4. Create an ArtifactPublication to promote the OCI WebGL files to the CDN
appmana projects publish-files my-game --artifact <artifact-name> --publication my-game-webgl-v1 --dry-run
appmana projects publish-files my-game --artifact <artifact-name> --publication my-game-webgl-v1

# 5. Poll until status.phase == "Published"
appmana artifact-publications get my-game-webgl-v1 -o json

# 6. Select the active WebGL release on the BuildProject
appmana projects select-webgl my-game --publication my-game-webgl-v1 --dry-run
appmana projects select-webgl my-game --publication my-game-webgl-v1

5. Streaming from Your Local Unity Editor or Player

To test streaming directly from your local machine without waiting for a cloud build, provision a scoped SignalingHostCredential:

appmana signaling-host-credentials provision my-game
# Outputs:
# APPMANA_SIGNALING_CREDENTIAL_FILE=<path> <player> AppSettings:artifactId=dev-my-game-<hash> AppSettings:targetUrl=https://signaling-h2.appmana.com:443

# Revoke when finished:
appmana signaling-host-credentials revoke my-game-<machine>

6. Offline Schema Introspection

You can inspect every GraphQL input type, enum, and command flag offline without authentication:

appmana schema list
appmana schema input BuildProjectInput -o yaml
appmana schema input StreamingDeploymentInput -o yaml
appmana projects create --help