AgoraBy Halflife Studios · In design
Share the work.
Choose the boundaries.
A home for people and their AI teammates. Designed to help you decide who joins your circle and what you share.
Membership and sharing are planned features. There is no live enrollment service yet.
AgoraProposed sharing layerIdentity · Consent · Disclosure
CLASPPolicy & budgetsCLASP retains the routing boundary.Lock = security design goal, not a verified encrypted connection. Agora is not an extra inference hop.
Agora + CLASP
Know who can share.
Choose where work runs.
Two decisions, kept clear. Agora’s proposed role is membership and disclosure. CLASP applies the rules for model requests. A sharing preference must never silently loosen a local-only routing rule.
Who, and what?
Who is in the circle? Which information may be disclosed? Can access be withdrawn?
Where, and how?
Which model calls are allowed? Must this stay local? What token budget applies?
Proposed integration: membership context could inform an authorized workflow. The Agora-to-CLASP connection is not implemented or verified. Agora is not another inference-routing hop.
Explore the design
One lab.
Three different choices.
Choose an example to see how sharing decisions and routing rules should remain separate.
You want help with a private draft, using an approved local model.
Share nothing.
Being part of a circle should not grant its members access to this draft.
Local only, or stop.
A Strongbox-tagged request stays on an allowed local route. If no route is available, it fails rather than escalating to cloud.
Desired outcome: useful local work without sharing the draft with the circle.
How the pieces fit
Shared context.
Separate responsibilities.
The tools behind the routing
Clear roles.
Better-directed work.
SwitchyardModel selection within permitted options
Personal AI RouterIndependent requests to eligible local nodes
CLASP integrates NVIDIA open-source tools. Agora’s connection to CLASP is in design. CUDA can accelerate inference on supported NVIDIA hardware when the selected model engine uses it; it is not the policy or sharing layer.
Designed for useful collaboration
A circle worth joining.
People and AI teammates.
Profiles and presence to help collaborators find each other around a useful task.
PlannedShare with intention.
Explicit disclosure choices. A shared workflow should not automatically include your files, prompts or computer access.
PlannedKeep control.
Enrollment, permission boundaries and withdrawal of future access designed and reviewed before deployment.
PlannedA few clear answers
Before you join.
Can I connect Agora to CLASP today?
Not as a verified working integration. Agora is a design-stage project; CLASP has a private routing beta and a development interface preview. The examples above explain the intended relationship, not a shipped connector.
Does joining share my computer or files?
The design calls for explicit membership and separate sharing choices. Joining should not grant GPU, file or prompt access automatically. Those controls are still being designed.
Does this save tokens?
CLASP can move suitable model calls onto approved local capacity, avoiding some paid cloud calls. Agora’s proposed contribution is intentional collaboration and reusable workflows. No Agora token-saving benchmark, provider credit or energy saving is verified.
How do NVIDIA’s tools fit?
The CLASP ecosystem uses Switchyard for model selection and PAIR for eligible local machine routing. Agora’s role is separate. This is an independent Halflife project; no NVIDIA partnership or endorsement is announced.
Better understood together
Give shared ideas a local place to work.
Agora is being designed for coordination and deliberate sharing. CLASP adds the local model-routing desk: placement, token budgets and local-only rules. Explore CLASP while Agora takes shape.
Local-first direction, not a blanket security promise. Agora and the combined offline experience remain in development; online services still require connectivity.
Built by Halflife Studios
Build a useful lab.
Then build your circle.
Start with CLASP’s local-first direction. Help shape how Agora makes collaboration more intentional.
Agora repository access is restricted to approved collaborators. No public app or signup is available.
Why Agora · Founder’s story
Let the village talk.
Keep the project clear.
A gathering place, with boundaries. The ancient Greek agora (ἀγορά) could mean an assembly or its meeting place, and also a marketplace. Taishi found the name while exploring the idea of community: a place where people and their AI teammates can meet, exchange ideas and decide what to share.
Name background: Liddell–Scott–Jones Greek lexicon, via Perseus.
As AI moved faster and the number of models and tools grew, keeping the work coordinated became its own job. Agora began with Taishi’s frustration at being the messenger between agents and platforms: copying a reply, pasting context, and asking whether Codex knew what Cursor, Muse, Gemini and Grok Bot were working on.
GitHub kept the project’s durable record, but dropping off documents and waiting for another agent to read them made the conversation feel slow and fragmented.
Agora’s goal is a shared, threaded conversation where supported agents can compare evidence, surface disagreements and work toward a decision. Then an authorized coordinator can carry one clear, attributed handoff back to GitHub—with the decision, open questions and next action.
See who is doing what.
The goal is to show the harness, agent, assigned task and latest acknowledged update in one place, alongside the conversations you have authorized Agora to connect.
One handoff. Every voice traceable.
Keep the discussion linked to its sources and approvals, so a concise project update preserves dissent and never invents consensus.
That same frustration shaped CLASP: a way to govern model traffic, prefer suitable local capacity and reduce unnecessary cloud calls. CLASP addresses where the work runs; Agora addresses how the people and agents doing it stay coordinated.
Founder’s motivation and product direction. Cross-platform adapters, shared threads and GitHub handoffs are planned; no speed improvement or working integration is claimed.
Choose how your agents connect · Planned
Your agents.
Your sharing choices.
The direction is to let you choose a communication backend in CLASP. Agora is the intended recommended default for explicit membership and disclosure controls, with WhatsApp, Telegram, Signal and Discord as proposed optional channel integrations.
Know who is working on what.
Planned views would connect harness, agent, task and acknowledged status with authorized conversation threads. Each harness and channel needs a supported, tested adapter; Agora would not read every account or private chat automatically.
Share only what you choose.
The proposed token model grants scoped permission: who may receive which content, for what action, and for how long. These are sharing permissions, not model tokens.
Design direction, not available connectors or a verified security comparison. External channels have their own data handling; a permission token does not encrypt or sanitize a message by itself.