Piqo – a pi extension to collaborate with agents directly from your files
Piqo is a new extension for Pi that allows users to collaborate with language models directly from their files. It monitors specified directories for specific markers and generates content inline based on user instructions. This tool can be beneficial for tasks such as note-taking, writing, and research.
- ▪Piqo is a chat-less extension that integrates with Pi to facilitate collaboration with LLM models.
- ▪It automatically stores generated content back into the user's files after processing instructions marked with @piqo.
- ▪The extension supports various text file formats and can monitor multiple directories for changes.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
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 publisher | GitHub |
| Canonical URL | https://github.com/piqoni/pi-piqo |
| Publication time | Sat, 23 May 2026 17:30:42 +0000 |
| Retrieval time | 2026-05-23T17:37:27.536Z |
| Last seen | 2026-05-23T17:37:27.536Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | ahhcLhAnEmN3 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
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
Piqo — Pi Extension A chat-less way to collaborate with your favorite LLM models (remote or local), directly from your files and from any editor. The output is stored automatically into your files. It is a simple file-watcher extension for pi triggered on-save, which continously monitors directories for @piqo markers and uses the LLM to generate content inline. Might be useful for keeping notes, writing tasks, researching topics, etc. Random Example: If you write the following (highlighted line) and save the file: You will get something like (using gpt-5.4-mini): How It Works You start pi with the piqo extension and specify directories to watch Piqo recursively watches those directories for file changes When a file contains one or more @piqo <instruction> markers, it reads the file,…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.