@tpsdev-ai/flair 0.33.0 → 0.35.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/config.yaml +17 -0
- package/dist/cli.js +570 -83
- package/dist/component-env.js +286 -0
- package/dist/deploy.js +190 -3
- package/dist/doctor-client.js +370 -8
- package/dist/engine-version.js +239 -0
- package/dist/hook-install.js +39 -9
- package/dist/lib/auth-resolve.js +85 -2
- package/dist/lib/launchd-management.js +328 -0
- package/dist/lib/mcp-enable.js +19 -0
- package/dist/resources/AdminInstance.js +26 -8
- package/dist/resources/OAuth.js +41 -25
- package/dist/resources/auth-middleware.js +26 -0
- package/dist/resources/dcr-gate.js +194 -0
- package/dist/resources/mcp-handler.js +91 -4
- package/dist/resources/mcp-oauth.js +136 -7
- package/dist/resources/oauth-discovery.js +242 -0
- package/dist/resources/oauth-wellknown.js +111 -0
- package/dist/resources/rate-limit.js +400 -0
- package/docs/auth.md +122 -5
- package/docs/deploying-on-fabric.md +35 -2
- package/docs/deployment.md +1 -1
- package/docs/hosted-on-fabric.md +1 -1
- package/docs/mcp-clients.md +24 -2
- package/docs/troubleshooting.md +36 -0
- package/package.json +1 -1
package/docs/troubleshooting.md
CHANGED
|
@@ -104,6 +104,42 @@ date
|
|
|
104
104
|
|
|
105
105
|
If using the MCP server, restart Claude Code after rotating keys.
|
|
106
106
|
|
|
107
|
+
### "signing key ... could not be parsed as an Ed25519 private key"
|
|
108
|
+
|
|
109
|
+
**Symptoms:** `flair doctor` reports, naming the file:
|
|
110
|
+
|
|
111
|
+
```
|
|
112
|
+
⚠️ could not verify agent 'my-agent' registration — signing key
|
|
113
|
+
/home/you/.flair/keys/my-agent.key could not be parsed as an Ed25519 private key
|
|
114
|
+
(error:1E08010C:DECODER routines::unsupported)
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
**This is not a connectivity problem.** The failure happens locally, before any
|
|
118
|
+
request is sent — the instance is untouched. Checking ports, firewalls or the
|
|
119
|
+
Flair URL will not help. (Before #1023 doctor reported exactly this as
|
|
120
|
+
`instance unreachable`, and separately suggested passing `--agent`; neither was
|
|
121
|
+
the cause.)
|
|
122
|
+
|
|
123
|
+
**Causes:** the bytes in that file are not a private key Flair can read. Most
|
|
124
|
+
often either the file is truncated or corrupt, or it is not an agent key at all
|
|
125
|
+
— `~/.flair/keys/<id>.key` is also where the federation keystore writes its own
|
|
126
|
+
**encrypted** key files, which are not loadable as plain Ed25519 seeds.
|
|
127
|
+
|
|
128
|
+
**Fix:** identify which it is before touching the file — the two have opposite
|
|
129
|
+
remedies, and the wrong one loses a key.
|
|
130
|
+
|
|
131
|
+
```bash
|
|
132
|
+
# Is this id an agent, or a federation instance?
|
|
133
|
+
flair agent list
|
|
134
|
+
flair federation status
|
|
135
|
+
|
|
136
|
+
# If it IS an agent and the file is corrupt, re-register a fresh keypair:
|
|
137
|
+
flair agent rotate-key <agent-id>
|
|
138
|
+
```
|
|
139
|
+
|
|
140
|
+
If the id does not appear as an agent, leave the file alone — it belongs to the
|
|
141
|
+
keystore, and doctor simply has no business signing with it.
|
|
142
|
+
|
|
107
143
|
### Port conflict
|
|
108
144
|
|
|
109
145
|
**Symptoms:** `flair start` fails, "address already in use".
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tpsdev-ai/flair",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.35.0",
|
|
4
4
|
"packageManager": "bun@1.3.10",
|
|
5
5
|
"description": "Identity, memory, and soul for AI agents. Cryptographic identity (Ed25519), semantic memory with local embeddings, and persistent personality — all in a single process.",
|
|
6
6
|
"type": "module",
|