dsh-markji-bridge: Let DeepSeek Harness Agents Read and Write Markji Cards

What Does It Do?

Markji Bridge is a DSH plugin for DeepSeek Harness that gives agents a local cache of Markji (maimemo) decks, chapters and cards, so they can search, read, create, edit and archive cards without hitting the cloud API on every call. It solves the slow, conflict-prone and crash-unsafe nature of direct cloud writes: every edit is queued locally first, then synced with a pull, three-way merge and push order. The plugin ships 16 markji_* tools, is built only on Node built-in modules, is maintained by Oxmyxo and released under the MIT license.

Core Features

• Local SQLite cache: indexes, card bodies, the pending push queue, conflicts and sync tasks all live in a single cache.db, so daily search and reading never call the API.
• Plain-text search: each card also stores a plain-text column stripped of formatting, image/audio markers and base64, so search matches clean readable text only.
• Safe writes: edits are queued first, and before pushing the plugin pulls remote changes and performs a three-way merge, deduplicating conflicts per card so old data never overwrites the cloud.
• Background sync with crash resume: sync tasks return a handle immediately and report progress; after a crash or plugin restart the same handle resumes without creating duplicate cloud objects.
• Archiving and chapter management: cards move into an "archive" chapter of the same deck with an archive note inserted, and repeated calls are idempotent; chapters can also be created, renamed and sorted, and cards moved between them.
• Multi-process safety: several DSH processes on one machine can share a cache directory, with writes serialized through a file lock.

How to Use This Plugin?

Set the Markji OpenAPI token from the maimemo open platform in the DSH host process environment, then restart DSH. After enabling the plugin, call markji_decks to pull decks, markji_search to find cards by deck name or plain text, and markji_card_get to read a single card; create and edit with markji_card_create and markji_card_update, then start a background sync with markji_sync, check progress with markji_sync_status, inspect failures and conflicts with markji_failures, and resolve them one by one with markji_conflict_resolve. The first call pulls cloud data, after which reads come from the local cache; it requires the DSH 0.2.x host plugin environment and Node 22.13 or newer, and runs on Windows, macOS and Linux.

How to Troubleshoot This Plugin?

When cards still do not take effect after a sync, run markji_failures to see failed cards, conflicts and recovery suggestions, then follow those suggestions. For conflicts, use markji_conflict_resolve to keep local, keep remote or supply explicit content; conflicts are deduplicated per card and do not affect other cards. If a sync is interrupted, resume it with the resume option of markji_sync using the same handle so no duplicate cloud objects are created.