LocalFlow Core — Local-first data analysis with AI
Table of contents
- Overview
- Quick start
- Use an actual proxy
- API Reference
- Building
- Package structure
- Roadmap & changelog
- License
Overview
LocalFlow brings local-first data analysis to AI: your data stays on the device, and only metadata about it — column names, statistical samples, document structure — ever reaches the LLM. This is the metadata-first protocol: the model acts as a code generator, writing analysis code that runs locally, in a sandboxed browser iframe, on your real data. Raw data never crosses the inference boundary, results are deterministic (computed by code, not inferred), and a generated analysis can be saved and re-run on any compatible dataset with no further AI call.
📖 Full explanation of the metadata-first protocol — the metadata boundary, two-step execution, key properties, limitations and how it compares to classical cloud and local-model AI — is on the website: localflow.fr/metadata-first-ai.
Architecture overview
┌─────────────────────────────────────────────────────┐
│ Browser (client) │
│ │
│ ┌─────────────────┐ ┌──────────────────────┐ │
│ │ Host App / UI │ │ Sandbox │ │
│ │ (React or any) │ │ formula execution │ │
│ │ │ │ charts / maps │ │
│ │ LocalAssistant │◄────►│ fetch → proxy relay │ │
│ │ (vanilla JS) │ └──────────────────────┘ │
│ └────────┬────────┘ │
│ │ HTTPS (column stats + generated code) │
└───────────┼─────────────────────────────────────────┘
│
┌────────▼────────┐
│ LocalFlow Proxy │ (manages keys, auth,
│ │ whitelists APIs,
└────────┬────────┘ edge services: PDF, OCR...)
│
├──────────────────┐─────────────────────┐
│ │ │
┌────────▼────────┐ ┌───────▼───────┐ ┌───────────▼───────────┐
│ LLM API │ │ Whitelisted │ │ Your CRM / ERP / DB │
└─────────────────┘ │ external APIs │ └───────────────────────┘
└───────────────┘
What leaves the browser?
| Operation | Data sent | Where |
|---|---|---|
| Tabular analysis — code generation | Column headers + statistics | 🟠 LLM |
| PDF extraction | Raw PDF bytes | 🔵 Proxy |
| PDF analysis — code generation | Extracted document text | 🟠 LLM |
| Analysis execution | Actual data | 🟢 Browser |
| External API calls (optional) | Query parameters only | 🔵 Proxy |
🟢 Browser — stays in your browser · 🔵 Proxy — goes to your server only and proxied APIs · 🟠 LLM — forwarded to the AI model via your proxy
📄 For a deeper dive into these concepts, read the LocalFlow white paper.
Quick start — embedding LocalAssistant in your app
No server required — LocalProxy runs entirely in the browser and calls the LLM directly. See localflow-examples for complete React and vanilla JS apps you can run immediately.
1. Install
npm install @localflow/core
2. Create the assistant
import { LocalProxy, LocalAssistant } from '@localflow/core' // No server needed — LocalProxy calls the LLM directly from the browser const proxy = new LocalProxy() const assistant = new LocalAssistant({ proxy, llm: { protocol: 'gemini', // 'gemini' | 'openai' | 'anthropic' model: 'gemini-3-flash-preview', // optional, this is the default for Gemini }, // Point to the div where formula results should be rendered. // Accepts an HTMLElement, a CSS selector string, or a factory function. resultContainer: '#result', }) // Pass the user's API key — kept in the browser, sent only to the LLM provider. // With LocalProxy it is stored as-is (fine for development). With an actual // proxy (ProxyClient), the key is proxy-encrypted once, the clear key is // discarded, and only the encrypted form is ever stored or sent per request. await assistant.setLlmApiKey('AIza...') // Persist LLM config whenever it changes (user sets a new key, model, etc.) assistant.on('llm:change', (llm) => { if (llm.apiKey) localStorage.setItem('llm-key', llm.apiKey) })
To restore a key across page loads, pass it at construction:
const assistant = new LocalAssistant({ proxy, llm: { protocol: 'gemini', apiKey: localStorage.getItem('llm-key') ?? '' }, resultContainer: '#result', })
3. Load your data
// Tabular data — from any source: CSV parse, DB query, API response, etc. assistant.addDataset('portfolio', portfolioRows) // rows: Record<string, unknown>[] assistant.addDataset('market', marketRows) // Mark which dataset is the "active" one (the `data` variable in formulas) assistant.setActiveDataset('portfolio')
4. Send a message and render the result
With resultContainer configured, the assistant takes care of everything — creating the iframe, setting sandbox permissions, and relaying proxied API calls. No boilerplate needed.
assistant.on('message', (response) => { // Show response.answer in your chat UI appendChatBubble(response.answer) }) assistant.on('formula:done', ({ data }) => { // Optional: react to the formula's output data console.log('Analysis result:', data) }) // Send a message — the LLM generates a formula, and the assistant // renders it automatically in the configured resultContainer. const response = await assistant.prompt('Show me the allocation by asset class')
You can change the result container at any time:
assistant.resultContainer = document.getElementById('result') // or: assistant.resultContainer = '#result' // or: assistant.resultContainer = () => document.querySelector('.panel.active')
5. Save and replay formulas (optional)
Generated formulas are deterministic — you can save them and re-run on any compatible dataset without an additional LLM call.
// Get the formula code from the last response const formula = assistant.getLastFormula() // string | null // Save it to your catalog as an analysis object... saveToCatalog({ formula, title: response.title, description: response.description }) // ...and replay it later. executeFormula takes the formula *code* (a string), // so pass the `.formula` field of your saved analysis object: const saved = loadFromCatalog(/* ... */) assistant.executeFormula(saved.formula)
6. Register a semantic analysis-match hook (optional)
This lets the assistant inject a relevant past analysis as a system-prompt example before calling the LLM, improving output quality.
assistant.setAnalysisMatchHook(async (query, ctx) => { const analyses = catalogLoad() // your catalog store return findBestMatch(query, analyses, ctx.activeColumns) })
Use an actual proxy
LocalProxy is designed for local development and quick prototyping. For production — where you need session management, API governance, PDF extraction, BYOK key encryption, rate limiting, and data flow monitoring — replace it with a ProxyClient connected to a LocalFlow proxy server.
The proxy handles:
- Security and session management — authenticates users against your business systems (CRM, ERP, or guest sessions), manages session tokens, and encrypts API keys so secrets are never exposed to the browser
- API governance — defines which external APIs formulas may call; supports BYOK, per-source throttling, URL whitelisting, and OAuth 2.0 token exchange
- Server-side edge services — PDF text extraction, OCR, and other tasks better suited to a server than a browser
- LLM bridge — decrypts the user's API key at request time and forwards generation requests to the LLM
- Data flow monitoring — tracks and audits what data enters and leaves the sandbox
LocalAssistant accepts any implementation of the Proxy interface — switching from LocalProxy to ProxyClient requires no other changes.
Connect to the proxy
import { ProxyClient, LocalAssistant } from '@localflow/core' const proxy = new ProxyClient('https://your-proxy.example.com') // Authenticate — stores the session token on the proxy instance await proxy.connect('odoo', { url, database, login, password }) // or for a public/guest session: await proxy.connect('public', {}) // Save the token so the session survives a page reload localStorage.setItem('proxy-token', proxy.token!) // Restore on next load const proxy = new ProxyClient('https://your-proxy.example.com', localStorage.getItem('proxy-token')) await proxy.getSessionInfo() // throws if expired — re-authenticate if needed const assistant = new LocalAssistant({ proxy, llm: { protocol: 'gemini' }, resultContainer: '#result' })
Quick testing: a hosted instance is available at https://backoffice.daquota.io/demo — no account needed. You can start with a guest (public) session, or authenticate against your own CRM if you want to test with real data. That said, you probably don't want to point your production CRM at an instance you don't control; use a sandbox or test environment instead.
Self-hosting: for production use, run your own instance — see the localflow-proxy repository for setup instructions.
PDF extraction
PDF extraction requires a proxy (not available with LocalProxy).
// Extract text via the proxy, then load as a dataset const { text, pageCount } = await proxy.extractPdf(pdfBuffer) assistant.addPdfDataset('report.pdf', pdfBuffer, text, pageCount) assistant.setActiveDataset('report.pdf') const response = await assistant.prompt('Summarise the key figures')
Pass an optional searchString to receive only pages matching the query (plus one page of context either side):
const { text, pageCount } = await proxy.extractPdf(pdfBuffer, 'revenue')
Wire up external APIs (optional)
The proxy admin configures which external APIs analysis formulas may call. Users can opt in/out and supply their own API keys (BYOK) per API.
// Fetch the list of APIs the proxy admin has whitelisted const apis = await assistant.fetchApiConfigs() // Activate one for use in formulas assistant.activateApi('overpass') // If an API requires a user-supplied key (BYOK): // pass the plain key — the assistant encrypts it via the proxy internally. await assistant.setApiUserKey('my-api', plainApiKey) // Persist API preferences whenever they change assistant.on('prefs:change', (prefs) => { localStorage.setItem('api-prefs', JSON.stringify(prefs)) })
API Reference
LocalAssistant API reference
Constructor
new LocalAssistant(config: LocalAssistantConfig)
interface LocalAssistantConfig { proxy: Proxy // any Proxy implementation — LocalProxy or ProxyClient llm: LLMConfig // LLM backend configuration appContext?: string // app domain context prepended to the system prompt (e.g. what the data represents) darkMode?: boolean // passed to the formula sandbox (default: false) apiPreferences?: ApiPreference[] // previously persisted prefs (from 'prefs:change') resultContainer?: ResultContainer // where to render formula results sandboxPermissions?: string[] // iframe sandbox flags (see defaults below) sandboxTheme?: Record<string, unknown> // Tailwind theme object injected into the sandbox (see below) pdfFormulaRevision?: boolean // silent self-correction on first PDF query (default: false) formulaHealingRetries?: number // silent retries on JS syntax errors (default: 1) modelSize?: 'small' | 'medium' | 'large' // active model's capability tier; 'small' uses a lean code-only protocol for local/edge models (default: 'large') } interface LLMConfig { // --- BYOK (bring your own key) --- protocol?: 'gemini' | 'openai' | 'anthropic' | 'ollama' // 'openai' = any OpenAI-compatible endpoint; 'ollama' = Ollama's native /api/chat (needed to control a thinking model) model?: string // model ID — falls back to protocol default if omitted apiKey?: string // encrypted key restored from storage — set via setLlmApiKey() baseUrl?: string // override the protocol's default endpoint (LocalProxy only) // --- Server-managed model (ProxyClient only) --- modelId?: string // references a model defined in the proxy's llm-configs.json // the server resolves protocol/model/apiKey/baseUrl from it } // resultContainer accepts any of: type ResultContainer = HTMLElement | string | (() => HTMLElement | null) // ^ element ^ selector ^ factory (evaluated at render time) // Default sandbox permissions: const DEFAULT_SANDBOX = [ 'allow-scripts', 'allow-downloads', 'allow-modals', 'allow-popups', 'allow-popups-to-escape-sandbox', ]
Configuration
| Property / Method | Type / Returns | Description |
|---|---|---|
assistant.llm |
LLMConfig |
Read or replace the LLM configuration. Emits 'llm:change'. |
assistant.darkMode |
boolean |
Toggle dark mode in the analysis sandbox. |
assistant.resultContainer |
ResultContainer |
Where formula results are rendered. |
assistant.sandboxPermissions |
string[] |
iframe sandbox flags. |
assistant.pdfFormulaRevision |
boolean |
When true, the first formula for a new PDF is silently run, its logs collected, and a second LLM call revises it before anything is shown to the user. |
sandboxTheme (constructor only) |
Record<string, unknown> |
Tailwind theme object injected into the sandbox CDN config before it initialises. Use it to align generated UI with your host app's palette: override gray shades for dark-mode card surfaces, define a primary color referenceable via bg-primary / text-primary, etc. The sandbox body also picks up dark:bg-gray-900 dark:text-gray-100 automatically, so setting gray[900] and gray[100] covers the full background. Works with any host framework — just translate your design tokens to Tailwind color values. |
assistant.proxy (read-only) |
Proxy |
The proxy implementation passed at construction. |
setLlmApiKey(plainKey) |
Promise<void> |
Encrypt a plain API key via the proxy and store it. Emits 'llm:change'. |
Datasets
Datasets are ordered key-value pairs: name → array of row objects (tabular) or PDF document (with extracted text). The active dataset is exposed as the data variable inside formula code; all datasets are accessible via datasets['name'].
| Method | Returns | Description |
|---|---|---|
addDataset(name, rows) |
void |
Add or replace a tabular dataset. First added becomes active. |
addPdfDataset(name, buffer, extractedText, pageCount) |
void |
Add a PDF document. Pass the text returned by proxy.extractPdf(). |
removeDataset(name) |
void |
Remove a dataset. Active dataset moves to next available. |
updateDataset(name, rows) |
void |
Replace rows for an existing dataset. |
getDataset(name) |
rows | undefined |
Read rows for a named dataset. |
getDatasets() |
Record<string, rows[]> |
All datasets as a plain object. |
setActiveDataset(name) |
void |
Mark a dataset as active (data variable in formulas). |
getActiveDataset() |
{ name, type, rows, columns } | null |
Current active dataset. type is 'table' or 'pdf'. |
getActivePdfBuffer() |
ArrayBuffer | null |
Raw bytes of the active PDF. |
getActivePdfExtractedText() |
string |
Extracted text of the active PDF. |
getActivePdfPageCount() |
number |
Page count of the active PDF. |
clearDatasets() |
void |
Remove all datasets and reset active. |
assistant.addDataset('Sales Q1', salesRows) assistant.addDataset('Products', productRows) assistant.setActiveDataset('Sales Q1') const active = assistant.getActiveDataset() // { name: 'Sales Q1', rows: [...], columns: ['id', 'product', 'amount', ...] }
External APIs
The proxy admin configures which external APIs analysis formulas may call. Users can opt in/out and supply their own API keys (BYOK) per API.
| Method | Returns | Description |
|---|---|---|
fetchApiConfigs() |
Promise<ApiConfig[]> |
Fetch available APIs from the proxy and store them. |
setApiConfigs(configs) |
void |
Set API configs without a network call. |
getApiConfigs() |
ApiConfig[] |
Currently stored API configs. |
setApiPreferences(prefs) |
void |
Bulk-set user preferences (enabled flags + BYOK keys). |
getApiPreferences() |
ApiPreference[] |
Current user preferences. |
activateApi(id) |
void |
Enable an API for use in formulas. |
deactivateApi(id) |
void |
Disable an API. |
setApiUserKey(id, plainKey) |
Promise<void> |
Encrypt a BYOK key via the proxy and store it. Pass the plain key — encryption is handled internally. |
getActivatedApis() |
ActivatedApi[] |
APIs that are currently active (forced or user-enabled). |
Conversation
| Method | Returns | Description |
|---|---|---|
prompt(message, opts?) |
Promise<AssistantResponse> |
Send a user message. Builds system prompt, calls the LLM, appends to history, emits 'message'. |
getHistory() |
ConversationTurn[] |
Full conversation history. |
setHistory(turns) |
void |
Replace the conversation history (e.g. to restore a session). |
appendHistory(turn) |
void |
Append a single turn. |
clearHistory() |
void |
Reset conversation to empty. |
getLastFormula() |
string | null |
Formula code from the most recent model response. |
buildCurrentSystemPrompt(example?) |
string |
Build the system prompt for the current state without sending it. |
prompt() options
await assistant.prompt('Break down revenue by region', { exampleAnalysis: { // inject a catalog analysis as a system-prompt example formula: '...', title: 'Revenue by country (bar chart)', description: '...', }, })
AssistantResponse shape
interface AssistantResponse { answer: string // HTML description shown before the formula runs formula: string // JS code to execute in the sandbox title?: string // short title for the analysis description?: string // longer functional description dependencies?: { // declared data dependencies data: string[] // columns accessed on the active dataset datasets: Record<string, string[]> // columns accessed per named dataset } systemPrompt?: string // snapshot of the system prompt used }
executeFormula(formula: string): void
Renders a formula in the configured resultContainer. Takes the formula code (a string — e.g. an AssistantResponse.formula, or the .formula field of a saved analysis object), not an analysis object. Returns void; the result data is delivered via the formula:done event (see Events). Creates the sandboxed iframe, applies sandboxPermissions, wires up the proxy fetch relay, and emits formula:done / formula:error. Called automatically by prompt() when resultContainer is set.
// Manual execution (e.g. replaying a catalog analysis) assistant.executeFormula(savedAnalysis.formula)
executeFormulaSilently(formula: string): Promise<{ data: unknown; logs: string[]; error?: string }>
The headless counterpart to executeFormula. Runs the formula code in a hidden, off-screen iframe against the current datasets / active dataset — proxying fetch calls and PDF document data exactly like the visible sandbox — but renders nothing and emits no events. Instead of firing formula:done / formula:error, it resolves with the result directly:
data— the formula's returneddata(ornull)logs— capturedconsole.*output, prefixedLOG:/WARN:/ERROR:error— set when the formula threw or the 30s timeout elapsed; otherwiseundefined
It always resolves, never rejects — a thrown formula is an inspectable result, not an exception. Use it to run a saved analysis like a plain async function and get its raw data with no UI:
const { data, logs, error } = await assistant.executeFormulaSilently(saved.formula) if (error) console.warn('Formula failed:', error, logs) else use(data)
executeFormula |
executeFormulaSilently |
|
|---|---|---|
Renders into resultContainer |
✅ | ❌ (hidden iframe) |
Emits formula:done / formula:error |
✅ | ❌ |
| Returns | void |
Promise<{ data, logs, error? }> |
buildSandboxDocument(formula: string): string
Lower-level alternative to resultContainer / executeFormula: returns the full sandbox HTML document for a formula as a string, so you can drive the iframe yourself. Useful when you need fine-grained control over the iframe lifecycle — loading states, tabbed layouts, or rendering into a framework-managed element. You are then responsible for the iframe's sandbox attribute (see DEFAULT_SANDBOX above).
const { formula } = await assistant.prompt('Break down revenue by region') iframe.srcdoc = assistant.buildSandboxDocument(formula)
destroy(): void
Removes the managed iframe and cleans up all event listeners. Call when the assistant is no longer needed.
Analysis match hook
Register a function that the assistant calls before each LLM request to find a semantically similar past analysis. The result is injected into the system prompt as an example, improving output quality for recurring analysis patterns.
assistant.setAnalysisMatchHook(async (query, context) => { // context: { history, datasets, activeDatasetName, activeColumns } const best = await mySemanticSearch(query, myCatalog) if (!best || best.score < 0.3) return null return { analysis: best.formula, score: best.score } }) // Call it directly (e.g. to check before showing a suggestion UI): const match = await assistant.resolveAnalysisMatch('Show portfolio heatmap')
Events
assistant.on('message', (response: AssistantResponse) => { console.log('Formula ready:', response.formula) }) assistant.on('dataset:change', () => { renderTabBar(assistant.getDatasets()) }) // Persist LLM config whenever it changes assistant.on('llm:change', (llm: LLMConfig) => { if (llm.apiKey) localStorage.setItem('llm-key', llm.apiKey) }) // Persist API preferences whenever they change — covers activateApi, deactivateApi, // setApiPreferences, and setApiUserKey (which encrypts BYOK keys before storing). assistant.on('prefs:change', (prefs: ApiPreference[]) => { localStorage.setItem('api-prefs', JSON.stringify(prefs)) }) assistant.off('message', myListener)
| Event | Payload | When |
|---|---|---|
message |
AssistantResponse |
After each successful LLM response |
dataset:change |
(none) | After any dataset add / remove / update / clear |
formula:done |
{ data: unknown } |
Formula finished executing; data is the formula's returned data field |
formula:error |
{ message: string } |
Formula threw or called console.error |
llm:change |
LLMConfig |
After setLlmApiKey() or assistant.llm = .... The payload contains the encrypted key — safe to persist and pass back via llm.apiKey at construction. |
prefs:change |
ApiPreference[] |
After any API preference mutation (activateApi, deactivateApi, setApiPreferences, setApiUserKey). The payload contains encrypted BYOK keys — safe to persist as-is and pass back via apiPreferences at construction. |
configs:change |
ApiConfig[] |
After API configs are loaded or updated via fetchApiConfigs() or setApiConfigs(). |
history:reset |
(none) | Conversation history was cleared (e.g. because the active PDF changed). |
api:blocked |
{ url, hostname, apiConfig | null } |
Formula called a URL not in the activated API list and the request failed. apiConfig is set if the API is known but inactive, null if completely unknown. |
api:error |
{ url, hostname, apiConfig, reason } |
An active API returned a JSON error body (e.g. expired key, quota exceeded). reason is extracted from the response. |
data:local |
{ data: string, action: string } |
An action completed entirely in the browser. E.g. file loaded from disk, formula executed in sandbox. Emitted by the app layer. |
data:proxy |
{ data: string, action: string } |
Data was sent to the proxy server but not to the LLM. E.g. PDF extraction. Emitted by the app layer. |
data:llm |
LlmDataPayload |
Data was forwarded to the LLM. Categorical payload — no display strings. kind is 'table', 'pdf', or 'text'; always includes query (raw user message) and dataset (file/dataset name). Table events include columns: number; PDF events include pages: number. Import the type: import type { LlmDataPayload } from '@localflow/core'. |
data:api-proxy |
ApiProxyPayload |
A formula fetch was routed through the api-proxy — fired on every call (success and failure). Includes url, method, body (raw request body — what left the browser), apiConfig (matched API definition or null if unrecognised), and status (HTTP response status; undefined on network error). Import the type: import type { ApiProxyPayload } from '@localflow/core'. |
Proxy API reference
Proxy is the interface that both LocalProxy and ProxyClient implement. LocalAssistant depends only on this interface — you can supply any conforming implementation.
import type { Proxy } from '@localflow/core' interface Proxy { readonly token: string | null isConnected(): boolean connect(type?: string, config?: Record<string, unknown>): Promise<void> getSessionInfo(): Promise<unknown> isEncrypted(str: string): boolean encryptMessage(message: string): Promise<string> decryptMessage(message: string): Promise<string> callLLM(request: LLMRequest): Promise<LLMResponse> getAvailableLLMs(): Promise<LLMModelInfo[]> getApiConfigs(): Promise<ApiConfig[]> proxyApiCall(url: string, method: string, headers: Record<string, string>, body: string): Promise<Response> extractPdf(buffer: ArrayBuffer, searchString?: string): Promise<{ text: string; pageCount: number }> listObjectTypes(): Promise<CrmObjectType[]> getObjectMetadata(objectType: string): Promise<CrmObjectType> getData(objectType: string, fields: string[]): Promise<Record<string, unknown>[]> }
Attachments. An
LLMMessagemay includeattachments: LLMAttachment[], whereLLMAttachmentis{ name: string; mimeType: string; data: string }(datais base64 without thedata:prefix).ProxyClientforwards them and the proxy maps them into each provider's multimodal format. A proxy insafeModerejects any request carrying attachments — checkgetPublicConfig().safeModefirst.
Message context. An
LLMMessagemay also carrycontext?: string— machine-generated preamble for the turn (e.g. the previous formula run's execution trace). The proxy prepends it tocontentwhen forwarding to the model but excludes it from the per-message prompt-char limit, which bounds the user's own input (content) only.LocalAssistantsets this internally; callers rarely need it.
LocalProxy
Browser-only implementation. No server required — suitable for local development, testing, and demos.
import { LocalProxy } from '@localflow/core' new LocalProxy(config?: { apis?: ApiConfig[] geminiBaseUrl?: string // override Gemini API base URL (testing / custom deployments) geminiApiKey?: string // baked-in Gemini key used when no key is set on the assistant rateLimit?: { maxPerDay: number // per-browser daily cap (tracked in localStorage) storageKey?: string // localStorage key prefix — defaults to '_lf_rl' } })
geminiApiKey — a fallback Gemini key used when the assistant has no key set. Useful for demos where you want users to try the app without supplying their own key. The user's own key (set via assistant.setLlmApiKey()) always takes precedence.
rateLimit — per-browser daily cap enforced before each callLLM call when using the demo key. When the limit is reached, callLLM throws LocalProxyRateLimitError. Pair with geminiApiKey to prevent a single user from exhausting a shared demo key for everyone.
import { LocalProxy, LocalProxyRateLimitError, LocalAssistant } from '@localflow/core' const proxy = new LocalProxy({ geminiApiKey: 'AIza...', // shared demo key — visible in DevTools, use a limited one rateLimit: { maxPerDay: 20 }, // generous enough to evaluate, stingy enough to protect the key }) const assistant = new LocalAssistant({ proxy, llm: { protocol: 'gemini' } }) try { await assistant.prompt('Show me the top 10 by revenue') } catch (err) { if (err instanceof LocalProxyRateLimitError) { // show UI asking the user to enter their own key } }
LocalProxy supports three protocols — calls go directly from the browser to the provider's API:
| Protocol | llm.protocol |
Default model | Notes |
|---|---|---|---|
| Gemini | 'gemini' |
gemini-3-flash-preview |
geminiApiKey + rate limiting apply |
| OpenAI (or compatible) | 'openai' |
gpt-4o |
Any OpenAI-compatible endpoint via llm.baseUrl |
| Anthropic | 'anthropic' |
claude-opus-4-5 |
Extended thinking supported via options.thinking |
| Behaviour | Notes |
|---|---|
callLLM |
Calls the LLM provider directly from the browser. For Gemini, uses geminiApiKey if no key is set and applies the rate limit. |
getAvailableLLMs |
Returns [] — user configures the model directly via LLMConfig. |
encryptMessage / decryptMessage |
No-ops — the key is stored and used as plain text |
extractPdf |
Throws — PDF extraction is not available in standalone mode |
listObjectTypes / getObjectMetadata / getData |
Return empty results — no CRM access |
connect / getSessionInfo |
No-ops — no session management |
Not for production use.
LocalProxyemits a console warning to remind you.
ProxyClient
HTTP client for a LocalFlow proxy server. Implements the full Proxy interface and adds session management.
import { ProxyClient } from '@localflow/core' const proxy = new ProxyClient(baseUrl, token?)
| Parameter | Type | Description |
|---|---|---|
baseUrl |
string |
LocalFlow proxy base URL (e.g. 'https://backoffice.daquota.io/demo') |
token |
string | null |
Optional — restore a previously saved session token |
Session
| Method | Returns | Description |
|---|---|---|
connect(type, config) |
Promise<void> |
Authenticate and store the session token. type is 'odoo', 'salesforce', or 'public'. config contains connector-specific credentials. |
getSessionInfo() |
Promise<unknown> |
Verify the current session. Throws if expired or not authenticated. |
getPublicConfig() |
Promise<{ safeMode: boolean; publicSessions?: { enabled: boolean } }> |
Read the proxy's public policy (no token needed). safeMode: true means the proxy never forwards attachments to the LLM — hide any "send file to AI" option. |
isConnected() |
boolean |
true if a session token is stored. |
proxy.token |
string | null |
The current session token — set by connect(), readable for persistence. |
proxy.baseUrl |
string |
The proxy base URL — mutable, can be changed before calling connect(). |
Encryption
| Method | Returns | Description |
|---|---|---|
isEncrypted(str) |
boolean |
true if the string is in the proxy-encrypted format. |
encryptMessage(plainText) |
Promise<string> |
Encrypt a string via the proxy. The result is safe to store and pass to the assistant. |
decryptMessage(cipherText) |
Promise<string> |
Decrypt a proxy-encrypted string. |
You rarely need to call these directly —
assistant.setLlmApiKey()andassistant.setApiUserKey()handle encryption internally.
PDF extraction
| Method | Returns | Description |
|---|---|---|
extractPdf(buffer, searchString?) |
Promise<{ text, pageCount }> |
Extract text from a PDF via the proxy. Pass an optional searchString to receive only pages matching the query (plus one page of context either side). |
CRM
| Method | Returns | Description |
|---|---|---|
listObjectTypes() |
Promise<CrmObjectType[]> |
List all available CRM object types (without fields). |
getObjectMetadata(objectType) |
Promise<CrmObjectType> |
Fetch full metadata for one object type, including its fields. |
getData(objectType, fields) |
Promise<Record<string, unknown>[]> |
Fetch rows for a CRM object type. |
const types = await proxy.listObjectTypes() const meta = await proxy.getObjectMetadata('res.partner') const rows = await proxy.getData('res.partner', ['name', 'email', 'country_id'])
Building
Prerequisites: Node.js 20+ (only needed to build the library — at runtime it is browser-only)
cd localflow-core npm install npm run build # tsc → dist/ npm run dev # tsc --watch (development)
The standalone tsc build produces dist/ with .js and .d.ts files and is needed when publishing the library to npm. During development inside the monorepo, localflow-app uses a Vite alias pointing to the TypeScript source directly — no pre-build required.
Package structure
localflow-core/
├── package.json # name: "@localflow/core"
├── tsconfig.json # emits dist/ with .js + .d.ts
└── src/
├── index.ts # public exports
├── LocalAssistant.ts # the core class
├── Proxy.ts # Proxy interface contract
├── LocalProxy.ts # browser-only Proxy implementation
├── ProxyClient.ts # HTTP proxy client
├── theme.ts # default sandbox Tailwind theme
└── types.ts # all public TypeScript interfaces
Roadmap & changelog
- ROADMAP.md — what's planned and under consideration.
- CHANGELOG.md — release history.
License
Apache 2.0 — see LICENSE for the full text.
Copyright (c) 2026 LocalFlow (localflow.fr)