A blazing-fast HTTP Client with TLS fingerprint
A blazing-fast HTTP Client with TLS fingerprint
A blazing-fast HTTP Client with TLS fingerprint
React components for building web experiences
The official JavaScript SDK for the Persona Inquiry Flow.
React bindings for the Persona Inquiry Flow JavaScript SDK.
Node.js Client for Persona API
Launch a mobile native implementation of the Persona inquiry flow from React Native.
Persona theme for NodeBB
A thin command-line front end for the workload-router. Spawns the harness CLI (`claude`, `codex`, `opencode`) configured by a selected **persona** from the project-local layer, configured source directories, or the small internal built-in system catalog.
Routing and profile utilities for AgentWorkforce workload orchestration.
Persona-kit owns the AgentWorkforce persona instantiation lifecycle. See tracking issue [#64](https://github.com/AgentWorkforce/workforce/issues/64).
Relay-maintained AgentWorkforce personas for use with `agentworkforce install`.
Shared webhook runtime primitives for normalizing provider events, registering local or HTTP consumers, and fanning events out consistently.
System prompt assembly and persona resolution for Grackle agent sessions
Composable primitives for spawning a persona's harness (claude, codex, opencode) with its MCP servers, env vars, and permissions wired up correctly.
Authentication in Playwright using personas.
A node.js verification library for local verification of BrowserID assertions.
Ei - Local-first AI companion with persistent personas
Faceted Prompting — structured prompt composition for LLMs
A persona component for Chakra UI
AI persona feedback tool for web pages — visit a page as a simulated persona and get reactions, friction points, and suggestions.
A blazing-fast HTTP Client with TLS fingerprint
Jobs-to-be-done enforcement for UI changes
This gem provides a lightweight single-sign-on authentication framework to a Rails application based on Mozilla's Persona service (see: https://login.persona.org/about). Persona identifies users by email address and authenticates them using the BrowserID protocol. This lets a client prove they own an email address without exposing their browsing behaviors to the identity provider. This also frees the application from needing to securely handle and store user credentials.
pikuri-vectordb gives a pikuri-core agent a +vectordb_search+ tool over a local document corpus — agentic search, the agent decides when to retrieve. Ships a swappable backend (a pure-Ruby +Backend::InMemory+ for teaching, plus thin +Backend::Qdrant+ / +Backend::Chroma+ HTTP clients for persistence — Qdrant recommended), a chunker, an embedder wrapper over +RubyLLM.embed+, and an optional +Reranker::LlamaServer+ that speaks +/v1/rerank+ against a cross-encoder model. Text extraction goes through +Pikuri::FileType.read_as_text+ in pikuri-core, which handles plain text / Markdown / PDF; HTML extraction is a deferred follow-up. Hosts wire the feature via +c.add_extension Pikuri::VectorDb::Extension.new(...)+ inside the +Agent.new+ block — same opt-in shape as +pikuri-tasks+ / +pikuri-skills+. The bundled +Pikuri::VectorDb::LIBRARIAN+ persona is the privilege-separated sub-agent counterpart for hosts that want recall to flow through a child rather than the parent's context. Three model endpoints in the full setup — chat (via ruby_llm), an embedder (via +RubyLLM.embed+), and an optional reranker (HTTP +/v1/rerank+). A single +llama-server+ in router mode serves all three by default, loading each cached GGUF on demand; see the gem's README for details.