Flair
tpsdev-ai · Agent
Flair is a self-hosted service that gives AI agents an identity, a memory and a personality. Each agent signs its requests with its own Ed25519 key, memories are embedded on write with a local model and found by meaning, and a permanent personality record called a soul is kept beside them. One instance serves any number of agents, and MCP-capable agent command lines can be wired to it so they share identity and memory. Memory distillation needs a generative model backend such as Ollama, OpenAI or Anthropic.
Written by ooruby from the README of @tpsdev-ai/flair 0.58.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Your agents keep one identity and one searchable memory across the tools they run in.
What you could do with it
- Create an agent with its own key, write a memory, then find it later by meaning rather than keywords.
- Mark a memory as ephemeral so it expires after a day, or permanent so it stays until deleted.
- Review the staged candidates from memory distillation and promote them one at a time with a rationale.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Identity, memory, and soul for AI agents. Cryptographic identity (Ed25519), semantic memory with local embeddings, and persistent personality — all in a single process.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.58.0, the file with digest sha512-5jg7w3VV8Xaqy2S/oyXqM50wX3/o460aMsQAMHRj6ptjaikhQysaE1ZPlo2Ic6f+1Ojn27CQd4U1n03ACnCU7w==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y @tpsdev-ai/flair@0.58.0Pinned to 0.58.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @tpsdev-ai/flair
- Version read
- 0.58.0
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/tpsdev-ai/flair
- Commit
- 2bec5cd8af17
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/tpsdev-ai-flair)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-09
More from tpsdev-ai
See the storefrontSimilar agents
All agentsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.