HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
agentflare-ai
sqlite-graph
C2025–2025
agentflare-ai / sqlite-graph

sqlite-graph

SQLite Graph Extension

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

What to know before exploring

What it is

SQLite Graph Extension

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM 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 6-hour interval2 dated mentions

Observed mentions: 2025-10-29 18:52:46 UTC to 2025-11-03 20:41:07 UTC.

012025-10-29 18:00:00 UTC to 2025-10-30 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsOct 29, 18:002025-10-30 00:00:00 UTC to 2025-10-30 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-30 06:00:00 UTC to 2025-10-30 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-30 12:00:00 UTC to 2025-10-30 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-30 18:00:00 UTC to 2025-10-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-31 00:00:00 UTC to 2025-10-31 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-31 06:00:00 UTC to 2025-10-31 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-31 12:00:00 UTC to 2025-10-31 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-31 18:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-01 00:00:00 UTC to 2025-11-01 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-01 06:00:00 UTC to 2025-11-01 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsNov 1, 06:002025-11-01 12:00:00 UTC to 2025-11-01 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-01 18:00:00 UTC to 2025-11-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-02 00:00:00 UTC to 2025-11-02 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-02 06:00:00 UTC to 2025-11-02 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-02 12:00:00 UTC to 2025-11-02 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-02 18:00:00 UTC to 2025-11-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-03 00:00:00 UTC to 2025-11-03 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-03 06:00:00 UTC to 2025-11-03 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-03 12:00:00 UTC to 2025-11-03 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-03 18:00:00 UTC to 2025-11-04 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsNov 3, 18:00

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
Oct 29, 18:002025-10-29 18:00:00 UTC2025-10-30 00:00:00 UTC110
Oct 30, 00:002025-10-30 00:00:00 UTC2025-10-30 06:00:00 UTC000
Oct 30, 06:002025-10-30 06:00:00 UTC2025-10-30 12:00:00 UTC000
Oct 30, 12:002025-10-30 12:00:00 UTC2025-10-30 18:00:00 UTC000
Oct 30, 18:002025-10-30 18:00:00 UTC2025-10-31 00:00:00 UTC000
Oct 31, 00:002025-10-31 00:00:00 UTC2025-10-31 06:00:00 UTC000
Oct 31, 06:002025-10-31 06:00:00 UTC2025-10-31 12:00:00 UTC000
Oct 31, 12:002025-10-31 12:00:00 UTC2025-10-31 18:00:00 UTC000
Oct 31, 18:002025-10-31 18:00:00 UTC2025-11-01 00:00:00 UTC000
Nov 1, 00:002025-11-01 00:00:00 UTC2025-11-01 06:00:00 UTC000
Nov 1, 06:002025-11-01 06:00:00 UTC2025-11-01 12:00:00 UTC000
Nov 1, 12:002025-11-01 12:00:00 UTC2025-11-01 18:00:00 UTC000
Nov 1, 18:002025-11-01 18:00:00 UTC2025-11-02 00:00:00 UTC000
Nov 2, 00:002025-11-02 00:00:00 UTC2025-11-02 06:00:00 UTC000
Nov 2, 06:002025-11-02 06:00:00 UTC2025-11-02 12:00:00 UTC000
Nov 2, 12:002025-11-02 12:00:00 UTC2025-11-02 18:00:00 UTC000
Nov 2, 18:002025-11-02 18:00:00 UTC2025-11-03 00:00:00 UTC000
Nov 3, 00:002025-11-03 00:00:00 UTC2025-11-03 06:00:00 UTC000
Nov 3, 06:002025-11-03 06:00:00 UTC2025-11-03 12:00:00 UTC000
Nov 3, 12:002025-11-03 12:00:00 UTC2025-11-03 18:00:00 UTC000
Nov 3, 18:002025-11-03 18:00:00 UTC2025-11-04 00:00:00 UTC110

What Hacker News says

2 sources

Show HN: AgentML – SCXML for Deterministic AI Agents (MIT)

Hey HN, We’ve been experimenting with how to make AI agents more deterministic, observable, and production-safe, and that led us to build AgentML — an open-source language for defining agent behavior as state machines, not prompt chains. My co-founder posted before but linked to the project website instead of the repo, so resharing here. AgentML lets you describe your agent’s reasoning and actions as a finite-state model (think SCXML for agents). Each state, transition, and tool call is explicit and machine-verifiable. That means you can: - Reproduce any decision path deterministically - Trace reasoning and tool calls for debugging or compliance - Guarantee agents only take valid actions (e.g. “never send a payment before verification”) - Run locally, in the cloud, or within MCP-based frameworks Example: ``` <?xml version="1.0" encoding="
Read the rest
UTF-8"?> <agentml xmlns="github.com/agentflare-ai/agentml" xmlns:openai="github.com/agentflare-ai/agentml-go/openai" version="1.0" datamodel="ecmascript" name="researcher"> <datamodel> <data id="papers" expr="[]" schema='{"type":"array","description":"Fetched papers from Hugging Face"}' /> <data id="summary" expr="''" schema='{"type":"string","description":"Summary of the papers"}' /> </datamodel> <state id="start"> <onentry> <log label="Researcher: " expr="`Fetching papers from Hugging Face and summarizing with OpenAI\n`" /> <openai:generate model="gpt-4o" location="summary" stream="false"> <openai:prompt>Summarize these recent AI/ML papers from Hugging Face: {{fetch "https://huggingface.co/api/daily_papers"}} Provide a concise summary of the key trends, breakthroughs, and developments in AI/ML research. </openai:prompt> </openai:generate> </onentry> <transition target="log_summary" /> </state> <state id="log_summary"> <onentry> <log label="Researcher Summary: " expr="summary" /> </onentry> <transition target="done" /> </state> <final id="done" /> </agentml> ``` We’re using this in Agentflare to add observability, cost tracking, and compliance tracing for multi-agent systems — but AgentML itself is fully open-source (MIT licensed). Repo: https://github.com/agentflare-ai/agentml Docs: https://docs.agentml.dev We also launched SQLite-Graph, a Cypher-compatible graph extension for SQLite, which will serve as the base for AgentML’s native memory layer. It’s also MIT licensed: https://github.com/agentflare-ai/sqlite-graph Would love feedback from anyone building with LLM orchestration frameworks, rule-based systems, or embedded MCP tool servers… especially around how to extend deterministic patterns to multi-agent coordination. — Jeff @ Agentflare
5 points · Open discussion
gwillen85·Oct 29, 2025Submission

Show HN: SQLite Graph Ext – Graph database with Cypher queries (alpha)

I've been working on adding graph database capabilities to SQLite with support for the Cypher query language. As of this week, both CREATE and MATCH operations work with full relationship support. Here's what it looks like: import sqlite3 conn = sqlite3.connect(":memory:") conn.load_extension("./libgraph.so") conn.execute("CREATE VIRTUAL TABLE graph USING graph()") # Create a social network conn.execute("""SELECT cypher_execute(' CREATE (alice:Person {name: "Alice", age: 30}), (bob:Person {name: "Bob", age: 25}), (alice)-[:KNOWS {since: 2020}]->(bob) ')""") # Query the graph with relationship patterns conn.execute("""SELECT cypher_execute(' MATCH (a:Person)-[r:KNOWS]->(b:Person) WHERE a.age > 25 RETURN a, r, b ')""") The
Read the rest
interesting part was building the complete execution pipeline - lexer, parser, logical planner, physical planner, and an iterator-based executor using the Volcano model. All in C99 with no dependencies beyond SQLite. What works now: - Full CREATE: nodes, relationships, properties, chained patterns (70/70 openCypher TCK tests) - MATCH with relationship patterns: (a)-[r:TYPE]->(b) with label and type filtering - WHERE clause: property comparisons on nodes (=, >, <, >=, <=, <>) - RETURN: basic projection with JSON serialization - Virtual table integration for mixing SQL and Cypher Performance: - 340K nodes/sec inserts (consistent to 1M nodes) - 390K edges/sec for relationships - 180K nodes/sec scans with WHERE filtering Current limitations (alpha): - Only forward relationships (no `<-[r]-` or bidirectional `-[r]-`) - No relationship property filtering in WHERE (e.g., `WHERE r.weight > 5`) - No variable-length paths yet (e.g., `[r*1..3]`) - No aggregations, ORDER BY, property projection in RETURN - Must use double quotes for strings: {name: "Alice"} not {name: 'Alice'} This is alpha - API may change. But core graph query patterns work! The execution pipeline handles CREATE/MATCH/WHERE/RETURN end-to-end. Next up: bidirectional relationships, property projection, aggregations. Roadmap targets full Cypher support by Q1 2026. Built as part of Agentflare AI, but it's standalone and MIT licensed. Would love feedback on what to prioritize. GitHub: https://github.com/agentflare-ai/sqlite-graph Happy to answer questions about the implementation!
35 points · Open discussion

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.