Everything needed to turn analysis into an asset

Build context, review execution, rerun changes, and deliver results that remain useful after the chat ends.

Analysis asset workflow

Start with the work product, then inspect the engineering underneath

Move a complete Workspace bundle

Export a portable Workspace with local data-folder files, MCP cache, and the Agent query ledger included by default, then import it for a handoff or a new machine. Export an unencrypted .lantide.zip with a readable README and analysis-context snapshot; imported data uses main/ and additional/ containers.

Keep complete execution snapshots

Preserve Plan-local query and Source Run steps beyond the 50-step conversation context window so formal execution remains inspectable.

Link Reports to External Delivery

Attach Report-owned pointer metadata for P4, KM, URL, or Other destinations without uploading, validating, or deleting the external content.

Verify across Workspaces safely

Let an external Agent read snapshot-safe artifacts in another Workspace without switching the writer Workspace or allowing live queries and writes there.

Rerun from the change

Use cache, Source Run, dependency DAGs, and lineage to understand impact and refresh downstream results.

Review and deliver analysis

Align the question and grain in a Plan, require human-controlled formal Execute, and preserve evidence and limitations in the Report. New formal Agent Reports must close an approved execution Plan; quick exploration and human-created GUI Reports remain available.

Archive instead of delete

Hide inactive workspaces from the sidebar while keeping content, data bindings, and version history. Archived workspaces are managed in one dialog and still count for import matching, and Restore Previous Version appears only when a recovery copy actually exists.

Link SQL evidence into documents

Reference saved SQL scripts and project documents from a Plan, Report, or Reference with standard Markdown links. Clicking opens the target without running SQL or creating cache; Planning can save a draft for review before Execute.

Update without losing work

Check for updates about every 24 hours and choose Update and restart, Skip this version, or Later. Unsaved edits in the main window and compare views are confirmed before any restart, and Preview releases are available from a manual check.

Restore from the same bundle

If you changed SQL, documents, or analysis history locally, restore them from the identical-snapshot bundle without raising the version. The pre-restore state becomes the single recovery copy, and only bundled physical files are restored.

Engineering behind analysis assets

For technical teams evaluating execution, permissions, and data boundaries

Custom ReAct Harness

State routing, state-filtered tool matrix, exploration budget soft cap.

Context Engineering

Summary/Detail dual channel, layered prompts, annotation and knowledge injection optimization.

Unified Query Layer

sqlglot rewriting, tab cache, Source Run DAG, deep lineage tracing.

Data Sources

Local CSV/Excel/Parquet and folders; PostgreSQL/MySQL/SQLite ATTACH; staged SQL Server/Azure SQL; cloud folders; MCP materialization.

Security Boundaries

Original sources remain read-only; formal Execute is human-controlled; cross-Workspace access is snapshot-only; memory can be fully disabled.