HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
earendil-works
pi
TypeScript2025–2026
earendil-works / pi

pi

AI agent toolkit: unified LLM API, agent loop, TUI, coding agent CLI

82Distinct people
101Mentions
2Explicit recommenders
121.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

AI agent toolkit: unified LLM API, agent loop, TUI, coding agent CLI

GitHub

Where it is used

  • OpenClaw — OpenClaw embeds the Pi SDK to run an AI coding agent inside its messaging Gateway. It uses Pi’s createAgentSession-based runtime to control sessions, tools, and streaming without external processes. Source

What people are saying

I love Pi . I have been building an agent using its agent harness https://github.com/earendil-works/pi/tree/main/packages/agen... . I love the simplicity .

manoji used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:59:52 AM UTC.

Pi: Virtual Models direct repository link

Read the discussion on HN. A full-thread summary is not available yet.

Mentions over time

HN mentions by month101 dated mentions

Observed mentions: 2025-11-16 20:54:39 UTC to 2026-10-29 13:42:01 UTC.

01020302025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 20252025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 5 mentions; 4 submissions, 1 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 28 mentions; 4 submissions, 24 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 commentsApr 20262026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 13 mentions; 4 submissions, 9 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 16 mentions; 2 submissions, 14 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC101
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC541
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC28424
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC826
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC10010
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC606
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC101
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC808
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC1349
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC404
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC16214

What Hacker News says

1 sources
I am working on solving the AI Code Provenance problem and I believe my repos may be the first that provides AI code provenance. See the following example: https://github.com/gitsense/gsc-cli/blob/main/internal/cli/r... Notice how the code block header attributes the model. The UUID can be traced to the conversation so everybody can tell exactly how the code came about. For this to work though, you need to use my chat app as it ensures you can't tamper with things if you are truly serious about AI code provenance. I also have a lot more human-focused method which is part of my CLI tool. https://github.com/gitsense/gsc-cli I am currently looking at making pi (https://github.com/earendil-works/pi) support AI code provenance, but for now if you want a more structured way to capture what you have done in an agent session that can be used in c
Read the rest
ode reviews and be carried forward as knowledge that lives inside your repository, I have gsc lessons The basic idea is, after you have finished chatting/working with the agent, you would work with it to identify lessons worth carrying forward. You can store your session if you want, but really, the lessons should be something that can help you review code better and to prevent future mistakes. I have a real working example at https://github.com/gitsense/smart-ripgrep This is a fork of the BurntSushi/ripgrep repository. It shows how you can use lessons to learn from past design decisions.
In AI demands more engineering discipline. Not less

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.