Omni-graph v0.2.8

Changes

• Explicit prepare command with safe supported migrations and per-store recovery results.
• Install/update prepares validated registered stores for existing API 1 applications.
• Interrupted migrations retain a usable new executable and completed-store outcomes.
• TypeScript SDK 0.1.0 with typed memory operations, connection policies, reconnection and caller-controlled retry keys.
• SDK installation, API, examples, error handling and application-upgrade documentation.

Upgrading from v0.2.7

The old self-updater only replaces the executable. After omni-graph update, run the new command once:

omni-graph prepare --registered --initialize --json

Or use the new curl/npx installer, which performs preparation directly. Subsequent self-updates include preparation. Unregistered or unavailable projects still need explicit preparation/reconnection. Restart old engine processes.

Integration API 1 and database schema 4 remain unchanged. Compatibility inspection remains read-only. Supported migrations retain verified backups; never delete a store to resolve a readiness error.

Install

curl -fsSL https://github.com/Rekabytes-Enterprise/omni-graph/releases/latest/download/install.sh | sh

npx --yes --package=https://github.com/Rekabytes-Enterprise/omni-graph/releases/latest/download/omni-graph.tgz omni-graph install

Install the SDK into a Node application:

npm install https://github.com/Rekabytes-Enterprise/omni-graph/releases/download/v0.2.8/omni-graph-sdk.tgz

The SDK does not install the engine. Node.js 20+ and ESM are required. Both npm tarballs are hosted on GitHub; neither package is published to the npm registry.

SDK guide: https://github.com/Rekabytes-Enterprise/omni-graph/blob/v0.2.8/sdk/README.md
Full changelog: v0.2.7...v0.2.8

Omni-graph v0.2.7

Changes

• Faster ordinary store opening and selective search/recall candidate loading.
• Recall benchmark covering relevance, latency, response size and scope isolation.
• Optional retry-safe memory creation: use remember --file memory.json --idempotency-key YOUR_OPERATION_KEY. Identical retries return the original result; changed payloads conflict. Memory, links, images and receipt commit together.
• Updated agent guidance and the application-independent integration contract.

Storage compatibility

This version uses SQLite schema 4. Existing schemas 1–3 migrate automatically on normal opening after a verified backup. Stop older Omni-graph processes before upgrading. Older executables cannot use a migrated store. Integration API 1 remains supported.

Keep the original image files readable and unchanged when retrying an image-bearing save. Standalone memories remain supported.

Install or update

curl -fsSL https://github.com/Rekabytes-Enterprise/omni-graph/releases/latest/download/install.sh | sh

npx --yes --package=https://github.com/Rekabytes-Enterprise/omni-graph/releases/latest/download/omni-graph.tgz omni-graph install

The npx distribution is hosted on GitHub Releases; the short npm registry package name is not published. Run omni-graph setup in existing projects to refresh bundled agent guidance.

Verification

Linux, macOS and Windows Verify CI passed on dev commit 83376ede508cb9959860ca45e7a2096d82b83d5d. The tag points to main merge commit 89f77299d7622785d7ae7d35fa2fc6071306341c.

Release PR: #2
Full changelog: v0.2.6...v0.2.7

Omni-graph v0.2.6

Compatibility discovery for integrations

Run omni-graph compatibility --json to identify the actual executable, supported API and database schemas, selected stores, capabilities, and required recovery action. Discovery does not create or migrate stores. Consumers can opt into API 1 structured errors with --api-version 1 --json; existing unversioned JSON errors keep their previous behavior.

The public integration guide and authoritative JSON schemas are included in the repository and npm tarball.

Safe schema upgrades

This release uses SQLite schema 3. Normal store opening automatically upgrades schemas 1 and 2 after creating a verified SQLite backup, including committed WAL data. Migrations are transactional per store. Writer guards and schema rechecks prevent historical connections from continuing ordinary writes after migration.

Stop older processes before upgrading stores. Do not roll back to an executable that cannot read schema 3. Restoring a matching backup requires stopping all processes and accounting for writes made since that backup. Discovery and normal-opening preflight use temporary storage proportional to the database/WAL size; inspection remains advisory during active writes.

Installation

curl -fsSL https://github.com/Rekabytes-Enterprise/omni-graph/releases/latest/download/install.sh | sh

npx --yes --package=https://github.com/Rekabytes-Enterprise/omni-graph/releases/latest/download/omni-graph.tgz omni-graph install

Existing installations supporting self-update can use omni-graph update, then check the exact executable path with compatibility --json. GitHub-hosted distribution only; this is not an npm registry publication.

See the integration contract and PR #1.

Omni-graph v0.2.5

Omni-graph v0.2.5 adds durable visual references to memories.

Images for UI work

• Attach PNG, JPEG or WebP images with captions; bytes are copied into the owning memory's SQLite store.
• Save new memories, links and images atomically with optional images: [{file, caption}] in remember --file.
• Manage existing references using image add, image list, image export, and image remove.
• Preview images in the Web UI and open the original size. Search, recall and show include metadata so agents can discover and inspect references.
• Preserve scope and protected remote-access rules; images are omitted from graph-refresh payloads.
• Include images only for explicitly shared memories in shared export/import bundles, validating checksums and ownership.
• Install a visual-reference guide that keeps approval status, viewport and intended design constraints explicit.

Supports eight images per memory, up to 8 MiB each. Images retain embedded metadata; redact private content before attachment or sharing. No OCR, resizing, or visual embeddings are performed.

Database compatibility

Back up memory stores before upgrading if older-binary compatibility matters. The first access automatically migrates SQLite schema 1 to 2 while preserving existing records. Older executables cannot open upgraded databases. Image-containing shared bundles also require this version or newer.

Update

omni-graph update
# Inside each initialized project:
omni-graph setup

Reload agent skills afterward. The TUI retains text guidance; inspect images through the Web UI or export them for an image-viewing tool.

Omni-graph v0.2.4

Omni-graph v0.2.4 lets automatic writers save a memory and its known relationships together.

Changes

• Add an optional links array to remember --file JSON requests.
• Use to for new → existing and from for existing → new; provide exactly one existing endpoint per entry.
• Commit the memory, supplied edges, supersession effects, and FTS entries in one transaction. Any validation or SQL failure rolls everything back.
• Keep standalone creation unchanged: omit links or use [] when no relationship makes sense.
• Reuse the existing link validation and preserve client/project privacy boundaries. Incoming links must share the new record's database; outgoing references to accessible broader scopes remain supported.
• Update agent instructions and skill guides to prefer the combined request for known relationships.

The response retains its top-level memory ID. No schema migration is required. Relationships discovered later still use link. Creation has no idempotency key; check existing state after a lost response before retrying.

Update

omni-graph update
# Inside each initialized project:
omni-graph setup

Reload agent skills afterward. Existing memories are preserved. See the README for the linked-creation JSON example.

Omni-graph v0.2.3

Omni-graph v0.2.3 improves how agents save connected, evidence-backed memories and adds community contribution guidance.

Memory skill

• Capture and connect records with explicit, verified relationship direction.
• Preserve source lineage, test conditions, and unresolved questions; distinguish derived reports from independent evidence.
• Audit missing links without inventing causality or forcing standalone memories into the graph.
• Install and refresh all three supporting guides for Codex, Claude Code, and Pi.
• Preserve custom files and reject symlinked guide destinations before setup writes.

Automatic integrations still need to follow the workflow explicitly. Record and link writes remain separate CLI operations.

Community

Adds bug/feature issue forms, a PR template with issue-closing references, SECURITY.md, SUPPORT.md, CODE_OF_CONDUCT.md, MAINTAINERS.md, and CODEOWNERS. Contributions continue to branch from dev and target dev. Repository security/review settings require separate administrator configuration.

Update

omni-graph update
# Run inside each initialized project to refresh its skill and guides:
omni-graph setup

Reload your agent skills or start a new session after setup. Existing memories are preserved.

For v0.2.0 or older, reinstall using the shell installer or GitHub-hosted npx tarball first. The short npm registry package name is not published.

Omni-graph v0.2.2

Full Changelog: v0.2.1...v0.2.2

Omni-graph v0.2.1

Full Changelog: v0.2.0...v0.2.1

Omni-graph v0.2.0

Full Changelog: v0.1.2...v0.2.0

Omni-graph v0.1.2

Full Changelog: v0.1.1...v0.1.2