SLM Text-to-SQL
Translates natural language questions into valid SQL queries against custom database schemas offline.
01 / Overview & Capabilities
Translates natural language questions into valid SQL queries against custom database schemas offline.
Key Features
- Offline schema parsing and SQL translation
- Dialect support: PostgreSQL, SQLite, MySQL
- Guarantees valid syntax without leaking data to external servers
02 / Standalone OS Harness Installers, CLI & Python SDK
In SLMAgents 2.0, SLM Text-to-SQL executes inside the 10-Plane Pure-CPU Agent Harness (slm_harness). Download a self-extracting Individual Agent + Harness OS Installer for macOS, Windows, or Linux (bundling slm_text_to_sql + slm_harness + the ./slm CLI), install the full 26-agent desktop suite, or install via Python pip:
1. Individual SLM Text-to-SQL + 10-Plane Harness Installers (All OSes)
slm_text_to_sql + slm_harness + ./slm CLIslm_text_to_sql + slm_harnessslm_text_to_sql + slm_harness + ./slm CLI2. Full 26-Agent Studio & Desktop OS Installers
3. 10-Plane Harness CLI (./slm) & Python pip Installation
# Option A: Install via PyPI or editable source with the 10-Plane Harness $ pip install slm-text-to-sql $ pip install -e ./slm_harness -e ./slm_text_to_sql # Option B: Run directly through the Unified 10-Plane Pure-CPU Harness CLI (./slm) $ ./slm ask "Write a SQL query for total sales in West region against @schema.sql" $ ./slm chat # Interactive Rich TUI with 18 slash commands (/trace, /models, /arena, /undo) $ ./slm serve # 100% Offline Web AI Studio + OpenAI /v1 API at http://127.0.0.1:7860
03 / 10-Plane Pure-CPU Harness Integration (slm_harness)
Rather than executing as an isolated prompt wrapper, SLM Text-to-SQL is natively orchestrated by the SLMAgents 2.0 10-Plane Pure-CPU Harness (via slm_harness.runtime.legacy_bridge and CascadeRouter). Every call benefits from hybrid llama.cpp GGUF (Q4_K_M) + Quantized INT4/INT8 CPU execution, watermarked LRU memory governance, grammar-constrained decoding, and deterministic verification at $0 API cost:
| Harness Plane | Subsystem | How It Powers SLM Text-to-SQL on Pure CPU |
|---|---|---|
| Plane 6 | CascadeRouter (<35ms) |
Stage 2 (DDL / SELECT / Schema AST Regex) & Stage 4 (ONNXPrefixEnumMasker Token-Trie) |
| Plane 2 & 5 | MemoryArena & Hybrid CPU Runtime |
Specialist Role: sql (Prem-1B-SQL GGUF Q4_K_M / Qwen2.5-Coder-1.5B INT4). Managed inside Watermark LRU MemoryArena (lite 2.6 GB / balanced 4.7 GB / power 8.2 GB) with zero-copy session sharing and automatic OOM tier step-down (8B -> 4B -> 3B -> 0.8B). |
| Plane 7 & 8 | Deterministic Verifier & Governance | Plane 7 Read-Only SQLite Execution Verifier (?mode=ro URI) + Levenshtein PRAGMA table_info Column Auto-Healing |
| Plane 1, 3 & 4 | Kernel, Artifact Scratchpad & 4-Tier Memory | SQLite WAL CheckpointStore (/fork, /rewind, /undo), content-addressed artifact://<sha12> handles to prevent prompt bloat, and hybrid SQLite FTS5 BM25 + HNSW vector memory. |
04 / Source Checkout (Git Sparse-Checkout)
Clone this agent alongside the 10-Plane Pure-CPU Harness (slm_harness) from the monorepo using Git sparse-checkout — no need to download all 26 agents:
Option 1 — Sparse Checkout with 10-Plane Harness (Recommended)
# 1. Create and enter a new directory $ mkdir slm_text_to_sql_workspace && cd slm_text_to_sql_workspace # 2. Initialise empty git repo and add remote $ git init $ git remote add origin https://github.com/t00114218-stack/SLMAgents.git # 3. Enable sparse-checkout for both slm_harness and slm_text_to_sql $ git sparse-checkout init --cone $ git sparse-checkout set slm_harness slm_text_to_sql # 4. Pull the 10-Plane Harness and agent source $ git pull origin main
Option 2 — Full Repository Clone
$ git clone https://github.com/t00114218-stack/SLMAgents.git $ cd SLMAgents $ ./slm doctor
Note: After checkout, install the harness and agent in editable mode with pip install -e ./slm_harness -e ./slm_text_to_sql or download the pre-packaged OS Harness Installer above.
05 / Configuration & API Reference
Constructor Parameters
Instantiate SLMTextToSQL with performance and runtime options:
| Parameter | Type / Default | Description |
|---|---|---|
model_path | str | None | Local GGUF (.gguf) or quantized ONNX model path managed by MemoryArena. Default: None (auto-resolved via slm_harness). |
temperature | float | 0.0 | Sampling temperature. Default: 0.0. |
top_p | float | 0.9 | Nucleus sampling threshold. Default: 0.9. |
max_tokens | int | 256 | Max token output limit. Default: 256. |
n_threads | int | 4 | CPU thread count. Default: 4. |
Methods
| Method Signature | Return Type | Description |
|---|---|---|
generate_sql(schema, query, ...) | str | Generates valid SQL query string from natural language prompt. |
Execution Parameters
Complete list of execution parameters accepted by the primary agent method:
| Parameter | Type / Default | Description |
|---|---|---|
schema | str | Database DDL creation schema string. |
query | str | Natural language user question. |
system_prompt | str | None | SQL dialect prompt override. Default: None. |
user_input | str | None | Additional SQL constraints. Default: None. |
temperature | float | 0.0 | Sampling temperature. Default: 0.0. |
top_p | float | 0.9 | Nucleus sampling probability. Default: 0.9. |
max_tokens | int | 256 | Maximum token limit. Default: 256. |
Quick Start
from slm_text_to_sql import SLMTextToSQL
sql_agent = SLMTextToSQL(temperature=0.0, top_p=0.9, max_tokens=256)
query = sql_agent.generate_sql(
schema="CREATE TABLE sales (id INT, amount DECIMAL, region TEXT);",
query="What is total sales in West?",
system_prompt="Dialect: PostgreSQL",
user_input="Add WHERE amount > 0 condition",
temperature=0.0,
top_p=0.9,
max_tokens=256
)
print(query)
06 / Verified Execution Logs
Diagnostic execution console output running locally on CPU:
→ INPUT: Query: What is total sales in West? ← OUTPUT: "SELECT SUM(amount) FROM sales WHERE region = 'West' AND amount > 0;"