title: Setup and development description: Source-derived commands, dependency requirements, and the distinction between repository tool pins and the showcase host.

Setup and development

These procedures target the upstream application. The local showcase is a reader-facing adaptation, not a preconfigured character session.

The commands come from the checked-out manifests. Wiki authoring did not run installation, builds, native applications, or provider requests.

Separate repository metadata from host state

ContextRecorded valueMeaning
Root package.jsonpnpm@11.24.0Repository package-manager pin
.tool-versionsNode 26.7.0, pnpm 11.24.0, .NET 10Repository tool metadata, not this host’s installed versions
.github/CONTRIBUTING.mdNode 23+Upstream contributor guidance
Showcase hostNode v22.23.1, Corepack pnpm 11.24.0Owner-verified deployment/runtime choice reported for this integration

The host did not switch Node versions. The differing source metadata is not evidence that every workspace supports Node 22.23.1.

For a new development environment, use the source pins and the requirements of the selected application. The .NET entry concerns engine development, not a browser prerequisite.

Start with one application

Requirements include Git, Node.js, Corepack, pnpm, and network access for dependency installation. Desktop and mobile targets add platform-specific requirements.

  1. Clone https://github.com/moeru-ai/airi into a separate development directory.
  2. For the documented source snapshot, select commit 3da3cf815490b40521e24b22020954e7959d79b4.
  3. From the repository root, inspect the selected package-manager version.
corepack pnpm --version
  1. Install workspace dependencies.
corepack pnpm install

The root postinstall script installs Git hooks and runs build:packages. Installation therefore includes build work, not only package downloads.

  1. Start the browser application.
corepack pnpm dev

The root dev script selects @proj-airi/stage-web. Its package command uses vite --host. This development server is not a production access-control boundary.

Select another target

GoalCommand from the repository rootAdditional requirement
Browser with local HTTPScorepack pnpm dev:web:httpsLocal certificate support and browser trust
Desktop ver.corepack pnpm dev:tamagotchiA supported Electron environment and graphical session
Mobile Androidcorepack pnpm dev:pocket:androidAndroid development tools and a device or emulator
Mobile iOScorepack pnpm dev:pocket:iosApple development tools and a selected device or simulator
Shared UI storiescorepack pnpm dev:uiWorkspace dependencies
Upstream documentationcorepack pnpm dev:docsThe repository’s documentation workspace
Browser production buildcorepack pnpm build:webWorkspace build inputs and asset downloads
flowchart TD
    Source[Select the source revision] --> Tools[Resolve tool versions]
    Tools --> Install[Install workspace dependencies]
    Install --> Target[Choose one application]
    Target --> Web[Browser development]
    Target --> Desktop[Electron and native requirements]
    Target --> Mobile[Capacitor and device requirements]
    Web --> Session[Configure a real session]
    Desktop --> Session
    Mobile --> Session
    Session --> Providers[Provider, model, and optional voice]

Downloads and optional services

The web Vite configuration downloads the Live2D SDK and sample Live2D and VRM assets. A source checkout alone does not contain every required build asset.

A generation session needs a usable provider and model. Microphone input, local inference, and native speech add separate requirements. See providers-and-models and character-and-audio.

The hosted backend uses corepack pnpm dev:backend. The separate server channel uses corepack pnpm dev:server. Read services-and-integrations before starting either system.

Source context

See provenance for the source revision and the owner-reported host distinction.

Navigation: index · workflows · operations