Robin/openwiki-wiki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: daily update 2026-08-14

Browse Source
This commit is contained in:
OpenWiki Bot
2026-08-14 02:18:06 +08:00
parent 1737454ad1
commit 021e929b92
26 changed files with 290 additions and 154 deletions
Download Patch File Download Diff File Expand all files Collapse all files
themes.md
+1 -1
View File
@@ -19,7 +19,7 @@ Index kept narrow by design: only themes that map to Robin's actual work (life-s
| `MiniMax-m3` | MiniMax-M3 (1M context multimodal) HuggingFace model card + Twitter launch; the daily-driver inference provider behind every OpenWiki run and most of Robin's agent work; haimaker.ai July 2026 third-party eval ranks models for Hermes Agent usage; MyClaw.ai 2026-07-29 confirms M3 + M2.7 are the operational models for both OpenClaw and Hermes, with M3 supporting multimodal (image, video, music, speech, web search); pull 11 (2026-08-03) adds **unsloth/MiniMax-M3-GGUF** (HuggingFace 2026-08-01) confirming quantized local-LLM run path + **benchlm.ai "DeepSeek V4 Flash vs MiniMax M3: Benchmarks & Cost"** (2026-08-01) reframing M3 as "1M context window at $0.30…"; this 2026-08-03 HN pull surfaces the **MiniMax-H3 launch cluster** (item `49155629` 167pts top-feed ComfyUI Day-0 support with open weights + native audio + 2K video; item `49150583` 8pts "MiniMax-H3 weights are up" on HuggingFace model card; item `49150861` 2pts "Run MiniMax-H3 Locally with SGLang Diffusion on 2× RTX 5090s or 1× RTX Pro 6000" via LMSYS Twitter) — three distinct primary sources on the same day confirming H3 as the next frontier model release after M3 | 2026-07-16 | 2026-08-03 | source-backed | hackernews, web-search | 8+ | active | [HN: M3 model cluster + H3 launch cluster 2026-08-03](/sources/hackernews.md); [Tavily: Hermes Agent best-models eval](/sources/web-search.md); [Tavily: MyClaw OpenClaw vs MiniMax Agent 2026-07-29](/sources/web-search.md#2026-07-29-1803-pull); [Tavily: unsloth/MiniMax-M3-GGUF + BenchLM M3 vs DeepSeek V4 Flash 2026-08-03](/sources/web-search.md#2026-08-03-1808-pull) |
| `hermes-agent-v0-19-quicksilver` | Hermes Agent v0.19 "Quicksilver" release (2026-07-25): first-token delay 4.3s → 0.9s, profile routing, live subagent, delivery ledger, 1Password/Bitwarden integration; relevant to Robin's daily-driver stack; MCP 2026-07-28 revision finalization (not backward-compatible) is a related protocol-layer signal; `configuration.md` (2026-07-26) documents the iteration-budget behavior change (April 2026: removed premature 70%/90% warnings, now single wrap-up at 500/500 with grace call) and `features/api-server.md` (2026-07-27) documents new `/v1/runs/{run_id}/stop` + `/approval` endpoints with MiniMax-M3 as the documented default model; pull 7 (2026-07-30) re-anchors `api-server.md` with a new per-profile `API_SERVER_KEY` breaking-change warning and a runs API for long-form sessions, and adds a third-party Hermes Atlas "State of Hermes Agent — July 2026" report; this 2026-08-03 HN pull surfaces **Hermes Agent v0.20.0** (item `49159200`, NousResearch GitHub releases tag `v2026.8.3`, 1pt on HN day-of — the next major version after v0.19 Quicksilver); pull 11 (2026-08-03) adds a **Hermes Agent 0.19.1 GitHub bug report** (NousResearch issues/77000, 2026-08-02, score 0.790, "gpt-5.6-luna + opencode-go") confirming patch-version activity on the v0.19.x track between the v0.19 Quicksilver release and the v0.20.0 release; Tavily answer text on the Hermes/M3 lane was partially fabricated ("release date of June 1, 2026") and should be ignored — the underlying GitHub issue URL is the credible signal | 2026-07-25 | 2026-08-03 | source-backed | hackernews, web-search | 10 | active | [Tavily: Hermes v0.19 Quicksilver + MCP revision 2026-07-27](/sources/web-search.md); [Tavily: hermes-agent configuration.md + api-server.md + MyClaw 2026-07-29](/sources/web-search.md#2026-07-29-1803-pull); [Tavily: api-server.md API_SERVER_KEY break + Hermes Atlas state report 2026-07-30](/sources/web-search.md#2026-07-30-1804-pull); [Tavily: Hermes Agent 0.19.1 GitHub bug report 2026-08-03](/sources/web-search.md#2026-08-03-1808-pull); [HN: Hermes Agent v0.20.0 release 2026-08-03](/sources/hackernews.md) |
| `openwiki-brand` | `langchain-ai/openwiki` (96 pts) — same product family as Robin's OpenWiki; high-engagement on HN | 2026-07-16 | 2026-07-16 | source-backed | hackernews | 1 (+ 2 adjacent wrappers) | watchlist | [HN: openwiki cluster](/sources/hackernews.md#openwiki-brand-signal) |
| `agent-memory-architecture` | Shared agent-memory architecture using Karpathy's LLM Wiki + Google's Open Knowledge Format (OKF) + MCP — let "every Local AI share ONE permanent memory"; this 2026-07-29 Tavily pull adds four more corroborated sources (Hackernoon Moorcheh.ai "Agent Memory Has a Lock-In Problem. Open Formats Are How We Fix It." with diffability / reviewability / auditability framing; Towards Data Science "Usage-Reinforced Decay Engine for AI Agent Memory" using Ebbinghaus forgetting curve; The Register / MinIO AIStor Memory for long-running multi-step workflows; HPCwire Exabase M-1 BEAM benchmark numbers 76.9% / 75.0% / 68.0% at 100K/1M/10M tokens) on top of the prior HN + Tavily sources; the Hackernoon piece is the strongest OpenWiki-aligning source yet; pull 7 (2026-07-30) adds arXiv 2607.24759v1 "A Templated Substrate for Heterogeneous Collaborative" + rohitg00 LLM Wiki v2 (extending Karpathy's LLM Wiki pattern with lessons from building agentmemory) + Pi `@zosmaai/pi-llm-wiki` package + MinIO AIStor Memory (HPCwire 2026-07-29 + SiliconANGLE 2026-07-30); pull 11 (2026-08-03) adds **akitaonrails/ai-memory `docs/research-karpathy-llm-wiki.md`** (GitHub 2026-07-28, score 0.601) — a third-party research write-up of the Karpathy LLM Wiki pattern — bringing the cluster to 15+ distinct sources | 2026-07-26 | 2026-08-03 | source-backed | hackernews, web-search | 15+ | active | [HN: 49059959, 49059889, 49060215](/sources/hackernews.md); [Tavily: LLM Wiki + OKF cluster 2026-07-28](/sources/web-search.md); [Tavily: Moorcheh.ai + TDS + MinIO + Exabase cluster 2026-07-29](/sources/web-search.md#2026-07-29-1803-pull); [Tavily: arXiv 2607.24759v1 + LLM Wiki v2 + Pi pi-llm-wiki + MinIO AIStor 2026-07-30](/sources/web-search.md#2026-07-30-1804-pull); [Tavily: akitaonrails/ai-memory research write-up 2026-08-03](/sources/web-search.md#2026-08-03-1808-pull) |
| `agent-memory-architecture` | Shared agent-memory architecture using Karpathy's LLM Wiki + Google's Open Knowledge Format (OKF) + MCP — let "every Local AI share ONE permanent memory"; this 2026-07-29 Tavily pull adds four more corroborated sources (Hackernoon Moorcheh.ai "Agent Memory Has a Lock-In Problem. Open Formats Are How We Fix It." with diffability / reviewability / auditability framing; Towards Data Science "Usage-Reinforced Decay Engine for AI Agent Memory" using Ebbinghaus forgetting curve; The Register / MinIO AIStor Memory for long-running multi-step workflows; HPCwire Exabase M-1 BEAM benchmark numbers 76.9% / 75.0% / 68.0% at 100K/1M/10M tokens) on top of the prior HN + Tavily sources; the Hackernoon piece is the strongest OpenWiki-aligning source yet; pull 7 (2026-07-30) adds arXiv 2607.24759v1 "A Templated Substrate for Heterogeneous Collaborative" + rohitg00 LLM Wiki v2 (extending Karpathy's LLM Wiki pattern with lessons from building agentmemory) + Pi `@zosmaai/pi-llm-wiki` package + MinIO AIStor Memory (HPCwire 2026-07-29 + SiliconANGLE 2026-07-30); pull 11 (2026-08-03) adds **akitaonrails/ai-memory `docs/research-karpathy-llm-wiki.md`** (GitHub 2026-07-28, score 0.601) — a third-party research write-up of the Karpathy LLM Wiki pattern — bringing the cluster to 15+ distinct sources; **2026-08-13 HN pull** adds item `49286073` "Show HN: MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5" (46 pts, 22 cmts, github.com/fellowgeek/mcp-memory) — **the first HN item since the 2026-07-16 `langchain-ai/openwiki` brand signal to explicitly name Google's OKF frontmatter** (the same schema OpenWiki uses at `/index.md` frontmatter `okf_version: "0.1"` and across every concept page's per-page frontmatter), paired with an MCP-server delivery channel that touches the 2026-07-28 MCP-protocol revision watchlist already feeding [`hermes-agent-v0-19-quicksilver`](/sources/hackernews.md) Evidence cell — direct corroboration of the OKF+memory schema pattern rather than a new theme | 2026-07-26 | 2026-08-13 | source-backed | hackernews, web-search | 16+ | active | [HN: 49059959, 49059889, 49060215](/sources/hackernews.md); [HN: MCP Memory using Google's OKF 2026-08-13](/sources/hackernews.md#agent-memory-architecture-refreshed-this-run); [Tavily: LLM Wiki + OKF cluster 2026-07-28](/sources/web-search.md); [Tavily: Moorcheh.ai + TDS + MinIO + Exabase cluster 2026-07-29](/sources/web-search.md#2026-07-29-1803-pull); [Tavily: arXiv 2607.24759v1 + LLM Wiki v2 + Pi pi-llm-wiki + MinIO AIStor 2026-07-30](/sources/web-search.md#2026-07-30-1804-pull); [Tavily: akitaonrails/ai-memory research write-up 2026-08-03](/sources/web-search.md#2026-08-03-1808-pull) |
## Notes