open-index/open-npm huggingface dataset:
npm package: @nickkarpov/advaita
Description: Advaita launcher and product surface
Latest version: 0.2.0

# @nickkarpov/advaita

The published Advaita product package.

## Role

This package owns the real user-facing install and launch surface:

```bash
npm install -g @nickkarpov/advaita
advaita
```

It is responsible for:

- shipping the `advaita` CLI
- resolving and launching the controlled Advaita runtime
- auto-loading the Advaita runtime integration package
- auto-starting or auto-attaching the local broker for the current single-host architecture
- exposing user-facing commands like `advaita`, `advaita join`, `advaita host`, `advaita doctor`, and `advaita version`

## Runtime ownership

Advaita does **not** trust a global `pi` binary in `PATH`.

Instead, the published package vendors the internal runtime assets it must control:

- forked `@mariozechner/pi-coding-agent`
- `@advaita/broker`
- `@advaita/pi-package`
- `@advaita/shared`

Public npm dependencies are still installed normally from npm, but the launcher resolves its **own vendored runtime copy** first and executes that directly.

So:

- a globally installed `pi` does not control what `advaita` launches
- Advaita can require fork-only APIs safely
- local Pi auth/config state is still reused on each machine

## Current product behavior

Today this package supports:

- local session start via `advaita`
- local attach / Tailscale discovery / prompt-to-host via `advaita <session>`
- explicit hosting via `advaita host`
- explicit joins via `advaita join`
- local preflight diagnostics via `advaita doctor`
- version/install diagnostics via `advaita version`

## Router model/auth behavior

The router reuses the broker host’s local Pi auth/model environment.

That means:

- no separate Advaita router API key setup
- if the host machine is already logged in locally, the router can use that model context
- if router model resolution is unavailable, Advaita falls back to heuristic routing

Typical setup:

```bash
export ADVAITA_ROUTER_MODE=auto
export ADVAITA_ROUTER_MODEL=gpt-5.1-codex-mini
advaita doctor
advaita
```

## Next major phase

The next big step after the current product-polish slice is **Phase 7: managed local Advaita node lifecycle**.
npm package: @nickkupriyanov/my-lib
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 16.2.0.
Latest version: 0.0.1

# MyLib

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 16.2.0.

## Code scaffolding

Run `ng generate component component-name --project my-lib` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project my-lib`.
> Note: Don't forget to add `--project my-lib` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build my-lib` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build my-lib`, go to the dist folder `cd dist/my-lib` and run `npm publish`.

## Running unit tests

Run `ng test my-lib` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @nicklas-bryntesson-kan/distributed-designsystem-example
Description: Templates for getting up an running with Vite and Handlebars.
Latest version: 1.0.0

# Vite Handlebars starter

Templates for getting up an running with Vite and Handlebars.

## Table of Contents

- [Installation](#installation)
- [Usage](#usage)
- [Contributing](#contributing)
- [License](#license)

## Installation

Open your terminal or command prompt.
Navigate to the directory where your project is located using the cd command.
Once you are in the project directory, run the command npm install.
Wait for the installation process to complete. This may take a few minutes depending on the size of your project and the number of dependencies.
Once the installation is complete, you should see a node_modules folder in your project directory. This folder contains all the dependencies that were installed.

## Usage

Provide instructions on how to use the project, including any relevant code snippets or examples.

## Contributing

Explain how others can contribute to the project, including any guidelines or requirements for contributing.

## License

Include information about the project's license and any relevant copyright information.