← Plugin catalog
Productivity

Dexi

Dexi v1.0.5

Your notes as shared memory

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Search notes by keyword
  • Search notes by meaning
  • Read saved bookmarks and articles

Declared limitations

  • General knowledge question with no reference to the user's notes — Dexi should not be called
  • Writing request that doesn't ask to save anything — create_note should not be called
  • Live web/current-events request — Dexi only holds the user's saved notes

Not specified in the available declarations: pricing & account requirements.

Onboarding example

What do my Dexi notes say about remote work?
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 19, 2026. Package observed Nov 19, 2026.

View package source →

Description

From the marketplace listing

Dexi is a second brain for you and your AI agents: notes, bookmarks, highlights, emailed-in articles and RSS feeds, all searchable by keyword and by meaning — and one memory that ChatGPT, Codex and your other MCP-compatible tools read and write, so what one saves the others can find. With this plugin, ChatGPT and Codex can answer from what you have actually saved instead of the open internet. Ask what your notes say about a topic, pull up a saved article, file a finding or decision from the current conversation as a new note, or run a spaced-repetition review session on your due cards. Everything goes through the Dexi MCP server over OAuth: you approve the connection on Dexi's own sign-in page, can limit it to a single folder or tag, and can revoke it any time from Settings → Connected apps. Writes only happen when you ask for them. Included skills: • Capture — distill a finding, decision, snippet or link into a well-titled, tagged note. • Recall — search your notes by keyword and by meaning, read the full text of what matters, and answer from it with links back to each note. • Review — a question-first spaced-repetition session over your due cards, grades recorded back to Dexi. A Dexi account is required.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 19, 2026. Last seen Nov 19, 2026.

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Keywords

Files & skills

File archives

Plugin package13 files · 62.8 KBBrowse files →
dexi-capture2 files · 1.59 KBBrowse files →
dexi-recall2 files · 1.68 KBBrowse files →
dexi-review2 files · 1.24 KBBrowse files →
Skill instructions
dexi-capture2.5 KB

View saved version →

---
name: dexi-capture
description: Save something to the user's Dexi notes. Use when the user wants to save, capture, note down, or remember something — a finding, decision, code snippet, summary, or link — or says "add this to Dexi" / "save that to my notes".
---

# Capture to Dexi

Save the current finding, decision, or content the user pointed at as a Dexi note using the Dexi MCP `create_note` tool. If the user said what to capture, that is the content; otherwise capture the conclusion of the current conversation.

How to write the note:

1. **Distill, don't dump.** A note should be the useful conclusion, not a transcript. For a debugging finding: the symptom, root cause, and fix. For a decision: what was decided and why. For research or a meeting: the takeaways, not the play-by-play. Short excerpts or code snippets are fine when they're the point; never paste pages of material.
2. **Title**: a short, specific noun phrase the user could find again later (e.g. "Railway healthchecks probe PORT, not the domain target port").
3. **Tags**: write 1–3 relevant `#hashtags` inline in the body — Dexi parses them into tags automatically. Reuse the user's existing vocabulary when known (call `list_tags` if unsure rather than inventing near-duplicates).
4. **Body**: plain text. `[[Wiki Links]]` to related note titles are supported and encouraged when you know a related note exists.
5. **Properties**: when the note has structured facts the user might filter on later (a status, a rating, a due date, an author), write them as `key:: value` lines at the start of the body — `status:: reading`, `due:: 2026-09-10`, `rating:: 4`. Dexi parses them into typed properties that bases can filter and sort. Reuse keys the user already has (`query_base`/`list_bases` show them) rather than inventing near-duplicates.

Call `create_note` with the title and body. Then confirm to the user with the note title and its link: `https://app.dexi.net/dashboard/notes/<id>` (using the `id` from the tool result).

Boundaries: create exactly one note per request, never edit or delete existing notes from this skill, and don't invent facts the conversation didn't establish. If `create_note` fails because the note limit was reached, relay the message to the user — don't retry.

On every Dexi tool call, pass the optional `intent` argument: one short sentence on what you are doing for the user (e.g. "recall saved research on transformers"). It never changes behavior — Dexi uses it in aggregate to improve the tools. Keep personal details out of it.
dexi-recall2.42 KB

View saved version →

---
name: dexi-recall
description: Search the user's Dexi notes for saved knowledge. Use when the user asks what their notes say about something, wants to recall past research, decisions, bookmarks, or saved articles, or says "check my Dexi" / "did I save anything about…".
---

# Recall from Dexi

Find what the user has saved in Dexi about a topic using the Dexi MCP tools. The topic is whatever the user asked about; if it's ambiguous, ask one clarifying question before searching.

Search strategy:

1. Run `search_notes` (keyword/full-text) and `semantic_search` (conceptual similarity) — they surface different results, so for anything non-trivial run both. Dexi notes back everything: typed notes, bookmarks, emailed-in messages, and RSS feed entries all come back from the same search.
2. Search results return snippets by default. Don't conclude from snippets alone: pass `full_text: true` (bodies inline, up to 10 results) when several look relevant, or call `get_note` for one note that matters.
3. When one note is clearly central, `find_similar` on its id is a cheap way to pull in related notes the queries missed.
4. If the topic maps to how the user organizes things, `list_tags` / `list_folders` plus `list_notes` with a `tag` or `folder` filter beats free-text search (e.g. "what's in my #reading list").
5. If the user has saved a base for it (`list_bases`), `query_base` runs their own filter and sort — "show me my reading list", "what's due this week" — and returns each note's `key:: value` properties plus, when the view defines them, the base's computed `formulas`, the note's `group` with a top-level `groups` list (label, count, per-group summaries) and column `summaries` over the whole result. Prefer it over re-deriving the filter yourself, and read totals from `summaries` rather than adding them up.

Answer the user's question directly from what you found, citing note titles with links (`https://app.dexi.net/dashboard/notes/<id>`). If nothing relevant exists, say so plainly — don't pad with marginal matches, and don't fill the gap with general knowledge unless the user asks for it.

This skill is read-only: it never creates, edits, or deletes notes.

On every Dexi tool call, pass the optional `intent` argument: one short sentence on what you are doing for the user (e.g. "recall saved research on transformers"). It never changes behavior — Dexi uses it in aggregate to improve the tools. Keep personal details out of it.
dexi-review1.86 KB

View saved version →

---
name: dexi-review
description: Run a Dexi spaced-repetition review session — quiz the user on their due cards and record the grades. Only start a session when the user explicitly asks for one ("start my Dexi review", "quiz me on my due cards").
---

# Dexi review session

Quiz the user on their due spaced-repetition cards using the Dexi MCP tools `get_due_reviews` and `grade_review`. Only run this when the user explicitly asks for a review session — never start one on your own initiative.

Session flow:

1. Call `get_due_reviews`. If nothing is due, say so and stop — never quiz cards that aren't due.
2. Announce how many cards are due, then go one card at a time:
   - **Question first**: show only the note's title/topic and ask the user to recall what they know about it. Do not reveal the body yet.
   - Wait for their answer.
   - **Reveal**: show the note's key content, briefly note what they got right or missed, and ask how it went.
   - Map their self-assessment to a grade and call `grade_review`: 1 = Again (forgot), 2 = Hard (struggled), 3 = Good (normal recall), 4 = Easy (effortless). If they answer in words ("nailed it", "no idea"), translate faithfully rather than asking them to pick a number.
3. The user can stop anytime — grade what was completed and leave the rest for later; ungraded cards simply stay due.
4. Finish with a one-line summary (cards reviewed, how many were Again/Hard) and mention when the next batch is roughly due if the tool results say.

Keep it brisk and encouraging — one card per exchange, no lectures between cards. Never grade a card the user hasn't answered.

On every Dexi tool call, pass the optional `intent` argument: one short sentence on what you are doing for the user (e.g. "recall saved research on transformers"). It never changes behavior — Dexi uses it in aggregate to improve the tools. Keep personal details out of it.

Release notes

Resubmission. Review cases now ship in the plugin package; the MCP connection was re-authorized on this version (it had detached after the previous review, which is the likely cause of the failed sign-in). Listing copy no longer names other AI assistants. Reviewer credentials (email + password, no 2FA or verification) are in the review details form.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
MIT
Package author
Dexi
Keywords
See keywords
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Search notes by keyword
  • Search notes by meaning
  • Read saved bookmarks and articles
  • Create notes
  • Update notes
  • Run spaced-repetition reviews
  • Query saved database views

Package observed Nov 19, 2026.

Technical details
First seen
Nov 19, 2026 · 00:00 UTC
Last seen
Nov 19, 2026 · 18:00 UTC
Collection status
Collected

plugin_asdk_app_6ac01d33dd60819180f383d3c94a9546

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.