Your first step.
A clearer AI workflow.

CLASP is a local policy gate and operator desk for model requests. It applies placement, privacy and token-budget rules. Switchyard helps choose a permitted model; PAIR routes eligible local work.

A token is a unit a model uses to represent input or output. For text, it may be a word, part of a word or punctuation. Different models split text differently. It is not a coin or a fixed unit of useful thought.

A prompt is your request. Context is the material available for answering it: instructions, conversation, documents and tool results. More pasted text is not automatically more useful.

API input may be counted again. Some providers support caching under specific conditions, but repeated text is not universally free and a chat subscription is different from API billing.

Keep a short, reviewed project brief and give your harness only the relevant details. The development preview keeps chat in its tab; persistent project memory and file retrieval are not established CLASP features.

No. It routes independent requests to eligible nodes. Each request runs on one node; it does not pool GPU memory or shard one model across your house.

The CLASP desk itself is not an NVIDIA GPU requirement. Your model runtime, operating system and chosen model determine whether a worker can serve the workload. Verify compatibility for each machine.

CLASP integrates NVIDIA’s open-source Switchyard and PAIR tools. No formal partnership, sponsorship or certification is announced.

Strongbox-tagged requests require a permitted local-only route or fail closed. It is not a claim of automatic secret redaction or an encrypted credential vault. A local network is not proof that every worker is trusted.

The direction is a free local core with optional setup help and services; service prices are unannounced. The core has an MIT license but remains a private beta. Models, electricity, hardware and any chosen cloud provider have separate costs.

Local tokens do not become cloud credits. You can reserve your own unspent budget for harder tasks. Estimated avoided API spend is not net savings or measured energy reduction. Energy claims require power measurements and a comparable baseline.

No. The current pre-cloud minify stage is a heuristic stub, not a proven general-purpose prompt optimizer. The notify hook is not a shipped interactive approval dialog. Do not treat either as an automatic guarantee of lower token usage or human review.

The development layout supports small screens, but native mobile apps and authenticated QR joining are planned. Task briefs are handed to harnesses; CLASP is not a custom scheduler. Persistent community scoreboards are planned; current session milestones reset.

Use the beta setup and download status. The repository is private and requires approved access. Do not assume an example release tag or installer exists.

Ancient Greek ἀγορά refers to an assembly, meeting place or marketplace. The name inspires a shared gathering place for people and AI teammates, with deliberate boundaries around what is shared. Read the origin story.

No automatic release is intended. The proposed flow is invitation, identity confirmation, explicit selection of recipient/content/channel/duration, then approved sharing. NFC and wearable support are concepts, not available integrations.

These are proposed integrations alongside other communication services. Each needs a supported adapter and explicit permission; signing in or connecting does not authorize access to every chat or recording.

The design calls for stopping future access when a grant is revoked; it cannot guarantee recall of copies already received or immediate revocation on disconnected devices. Keep independent backups and verify them before changes or deletion. Final service terms remain under review.

Halflife’s planned membership and disclosure layer for people and their AIs. It is in design, not a released application.

CLASP manages model requests. Agora explores membership and intentional sharing. It sits beside CLASP, not between CLASP, Switchyard and PAIR.

The design calls for explicit enrollment and sharing choices. There is no live Agora enrollment service today. Membership should not silently grant data or compute access.

There is no verified public release or signup. Approved collaborators can read the private Agora repository; others can ask Halflife about the project.

Check that you are signed into the GitHub account granted beta access. Confirm the repository and available release tag in DOWNLOAD.md. A private repository may appear missing; do not guess a version tag.

The desk may be running while its model backend is unavailable. Confirm PAIR and the configured model engine are running, and check their actual endpoint and advertised model. Starting CLASP with --allow-no-pair skips its startup probe; it does not create a model backend.

Confirm each intended worker has a compatible model engine and model, and follow NVIDIA’s PAIR pairing instructions. CLASP’s gateway model list does not prove the identity or health of every LAN computer.

Try a smaller compatible model, shorter context or fewer concurrent jobs. Compare answer quality as well as speed. Record the exact model, runtime and task before recommending a hardware upgrade.

Include OS, CLASP version or commit, model runtime and version, model name, a short non-private reproduction and a sanitized error. Remove prompts, API keys, tokens, serial numbers, personal files and network identifiers you do not want shared.

CLASP governs model calls: placement, budgets and local-only routing. Agora is being designed around people and AI teammates: shared task visibility, conversations and explicit disclosure. The intended combination helps you direct the work and coordinate the team. It is not yet a shipped connector or a required bundle.

No. Start with CLASP and a suitable configured local model. Explore Agora when you want the planned collaboration layer. There is no public Agora installer or verified combined signup service today.

No. Local offline use after initial verification is the requirement for both products. Configured CLASP local routes need their models and local services available; Agora’s offline verification, identity and sharing behavior remains planned. Cloud models, external messaging and new downloads require connectivity. Offline operation alone does not guarantee security.