HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
inferablehq
inferable
TypeScript2024–2025
inferablehq / inferable

inferable

Build reliable AI Workflows and Agents with humans in the loop, structured outputs and durable execution.

2Distinct people
8Mentions
0Explicit recommenders
450GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Build reliable AI Workflows and Agents with humans in the loop, structured outputs and durable execution.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

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

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

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

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week8 dated mentions

Observed mentions: 2024-12-05 23:00:20 UTC to 2025-02-06 21:32:27 UTC. Weeks start Monday, UTC.

0122024-12-02 00:00:00 UTC to 2024-12-09 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsDec 22024-12-09 00:00:00 UTC to 2024-12-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-16 00:00:00 UTC to 2024-12-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-23 00:00:00 UTC to 2024-12-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-30 00:00:00 UTC to 2025-01-06 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 302025-01-06 00:00:00 UTC to 2025-01-13 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-13 00:00:00 UTC to 2025-01-20 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-20 00:00:00 UTC to 2025-01-27 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-01-27 00:00:00 UTC to 2025-02-03 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-02-03 00:00:00 UTC to 2025-02-10 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 3

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
Dec 22024-12-02 00:00:00 UTC2024-12-09 00:00:00 UTC110
Dec 92024-12-09 00:00:00 UTC2024-12-16 00:00:00 UTC000
Dec 162024-12-16 00:00:00 UTC2024-12-23 00:00:00 UTC000
Dec 232024-12-23 00:00:00 UTC2024-12-30 00:00:00 UTC000
Dec 302024-12-30 00:00:00 UTC2025-01-06 00:00:00 UTC101
Jan 62025-01-06 00:00:00 UTC2025-01-13 00:00:00 UTC101
Jan 132025-01-13 00:00:00 UTC2025-01-20 00:00:00 UTC101
Jan 202025-01-20 00:00:00 UTC2025-01-27 00:00:00 UTC211
Jan 272025-01-27 00:00:00 UTC2025-02-03 00:00:00 UTC110
Feb 32025-02-03 00:00:00 UTC2025-02-10 00:00:00 UTC110

What Hacker News says

1 sources
Yes! I've worked on something [1] in the space lately, and can share learnings. It generates queries, which gets fed to the application layer, and it executes them based on some deterministic controls. Basically, if you're working with a database that has some actually useful/critical data, put an application layer in the middle that can gatekeep LLM access. - Depending on your risk appetite, make a decision on providing a read-only URL to the thing that interfaces with the LLM. - For maximum control over the queries, you can wrap then in functions (tools) and let the LLM only call the tools. But this takes away a lot of the power. What we've basically done is allowing the LLM to read the context progressively [2] and give it free reign over the queries. - The said application layer can ask for approval on all of the queries. (Human in th
Read the rest
e loop). [3] - (Optionally) If your query returns a lot of data, putting all of that through the LLM context might be expensive. You need a way to return data out of band from a query, directly to the user. [1] https://github.com/inferablehq/inferable/tree/main/data-conn... [2] https://github.com/inferablehq/inferable/blob/ec504b8593f41b... [3] https://github.com/inferablehq/inferable/tree/main/data-conn...
In Ask HN: How to Safeguard a LLM to SQL Prompt from SQL Injection?

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.