WeSearch

Show HN: Faaah – Filesystem as an AI Handler

·3 min read · 0 reactions · 0 comments · 2 views
Show HN: Faaah – Filesystem as an AI Handler
TL;DR · WeSearch summary

🗣️ FAAAH (Filesystem As An AI Handler) The simplest OpenAI-compatible LLM proxy you will ever need.™️ FAAAH allows you to reuse your AI Agent subscription as a generic OpenAI-compatible local server. FAAAH is dependency-free, implemented as a plain-text file protocol (UNIX-philosophy certified): Instead of sending your prompts to cloud LLM APIs, send them to FAAAH, which reads OpenAI-compatible requests and dumps them into a folder as .txt files. Then, tell your existing AI coding agent (Claude Code, opencode, etc) to read the files and write responses to other .txt files.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 4,119 of its stories.

Original article
GitHub
Read full at GitHub →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherGitHub
Canonical URLhttps://github.com/sebastiancarlos/faaah
Publication timeSat, 08 Aug 2026 23:13:46 +0000
Retrieval time2026-08-08T23:20:42.329Z
Last seen2026-08-08T23:20:42.329Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterqBLWwT1FqogM · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

🗣️ FAAAH (Filesystem As An AI Handler) The simplest OpenAI-compatible LLM proxy you will ever need.™️ FAAAH allows you to reuse your AI Agent subscription as a generic OpenAI-compatible local server. FAAAH is dependency-free, implemented as a plain-text file protocol (UNIX-philosophy certified): Instead of sending your prompts to cloud LLM APIs, send them to FAAAH, which reads OpenAI-compatible requests and dumps them into a folder as .txt files. Then, tell your existing AI coding agent (Claude Code, opencode, etc) to read the files and write responses to other .txt files. FAAAH then packages the responses into OpenAI-compatible JSON, and returns them to your app. Why? Because you already pay for an AI coding assistant.

Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from GitHub