ChatGPT Inbox Community

by DAVID
5
4
3
2
1
Score: 28/100

Description

Create Markdown notes in Obsidian through a paired MCP relay or Lite links. Independent community plugin.

Reviews

No reviews yet.

Stats

0
stars
96
downloads
0
forks
23
days
4
days
4
days
8
total PRs
1
open PRs
0
closed PRs
7
merged PRs
1
total issues
1
open issues
0
closed issues
15
commits

Latest Version

5 days ago

Changelog

0.6.0 — lectura autorizada en relay

  • Incorpora leer_nota y consultar_lectura por el relay autenticado, con respuesta caducable y restricción a carpetas autorizadas.
  • Añade permiso independiente Permitir lectura de notas, desactivado por defecto y solo visible en modo relay.
  • Protege lecturas revocadas, caducadas, fuera de ámbito y duplicadas; preserva creación, edición y adjuntos anteriores.
  • El contenido de notas NO se envía a GitHub mediante esta función. El relay recibe temporalmente el texto autorizado.
  • Para usar lectura hace falta desplegar por separado el relay actualizado, emparejarlo y activar permiso en Obsidian; instalar solo este plugin no cambia el relay ni habilita lectura.
  • La aceptación funcional con un iPhone real se realiza después de la instalación, antes de habilitar el uso habitual.

0.5.0 — unified receiver candidate

  • Consolidate version-checked editing, recoverable trash/restore and verified binary attachments in Advanced GitHub mode. Relay/Lite stay create-only.
  • Keep expanded permissions opt-in, enforce scope/lifecycle guards around asynchronous work, persist idempotent local receipts and retain previous note versions.
  • Remember the GitHub secret selection per device, check automatically after selection and recover if secret storage becomes available after initial layout.
  • Use portable SHA-256 for binary integrity on mobile WebViews without crypto.subtle.
  • Preserve create-only delivery, Relay OAuth/receipt handling and the public plugin identity. A migration preserves private history/ledger and secret identifiers; the private receiver is disabled, not deleted.

Automated validation and the iPhone acceptance results are tracked separately. This source change does not publish a release or deploy a relay.

0.4.4 — reception reliability candidate

  • Separate verified local notes awaiting a relay receipt from confirmed delivery, conflicts and blocked requests.
  • Cancel outstanding receiver waits on background/offline/unload, fence stale mode results, bound network requests to 20 seconds and retry transient failures with capped backoff.
  • Respect the normal interval on repeated focus events and resume reception after interrupted checks.
  • Check the authorized default destination and available client authorization during setup; prevent concurrent pairing button actions.
  • Add an explicit synthetic note test with persistent idempotency key, normal scope/capacity/retention limits, real receipt lookup and local content/identity verification. Requires the separate relay to be updated to 0.4.4; older relays retain ordinary reception.
  • Add a local diagnostic report containing only versions, states, timestamps and counts, with review/selection and no automatic upload.
  • Correct the published 0.4.3 documentation state and record mobile acceptance limits.

147 automated tests, full Obsidian lint/typecheck/build and a native Obsidian 1.14.5 relay/client/receipt acceptance passed locally. PostgreSQL CI is required before release. Physical iPhone acceptance remains pending. This source tree is a candidate; no 0.4.4 publication or production relay deployment is implied.

0.4.3 — review correction candidate

  • Validate JSON envelopes, relay replies, GitHub listings/blobs and saved settings/history from unknown inputs before use. Preserve valid settings, secrets by identifier, receipts and create-only delivery.
  • Searchable declarative settings and public update API; no deprecated display override.
  • History search traverses only authorized subtrees and rechecks scope before content reads. Folder selection still needs local metadata enumeration.
  • Remove clipboard APIs; select generated instructions for native copy on macOS/iOS.
  • Run the full Obsidian recommended lint preset and unsafe TypeScript checks in CI. TypeScript 6.0 is used because the current TypeScript ESLint parser supports versions below 6.1.
  • Pin the development dependency override for patched moment; runtime plugin bundle remains browser-only.
  • 122 automated tests, typecheck, build and lint passed locally. Desktop settings layout, settings search and native text selection were verified on Obsidian 1.14.5 in a disposable vault. Physical iPhone acceptance of this candidate is pending. PostgreSQL verification is also run by CI.
  • Add a draft-release workflow with build provenance attestations; attestations only exist after that workflow succeeds.

The official 0.4.2 scorecard showed 81 warnings and 6 other observations. Base64 decoding is required for GitHub blobs. Vault enumeration remains necessary for the explicit folder picker. Unavailable malware/obfuscation scans are scanner limitations, not results this repository can certify.

ChatGPT Inbox Community 0.4.1

Create Markdown notes through a paired OAuth/PKCE MCP relay, Lite links or an advanced GitHub inbox. Obsidian must be active to receive. No public hosted relay is included.

Changes

  • Fix browser OAuth consent: keep same-origin Origin on form submissions, allow the validated callback origin through form CSP, and encode CSP delimiters in unusual URL hostnames.
  • Add rotating refresh credentials, bound to the original client, resource and authorized scope. Reuse revokes the affected grant. Expiry is seven inactive days or thirty days from consent; an additional safety limit bounds rotation history.
  • Preserve registered DCR client IDs across reconnects. Snapshots made by older relays still load; existing access tokens continue until expiry, but users must authorize again to receive refresh credentials.
  • Retry initial PostgreSQL lease contention for up to two minutes. Pending/failed storage returns HTTP 503. Connection loss after loading remains terminal to prevent stale-snapshot writes.
  • Drain active requests and release storage on SIGTERM/SIGINT. The relay remains single-writer; deployments may briefly return 503 during handover and do not promise zero downtime.
  • Raise the declared minimum to Obsidian 1.14.5, the desktop version with native acceptance evidence. This does not certify every physical mobile scenario.
  • Update setup, privacy, operator instructions and acceptance evidence.

Existing behavior

Notes are create-only; folder permissions are checked on receipt, conflicts preserve existing files, retry keys avoid duplicates, and only delivered confirms a verified local write. The mobile bundle has no Node.js/Electron dependencies. Device secrets are not copied through data.json.

Upgrade

Update the relay as well as the Obsidian plugin. Reauthorize the MCP client once to obtain refresh credentials. Use a distinct secret and pairing on each receiving device. A compatible client handles subsequent refreshes; exact client behavior and account permissions still apply.

The published plugin is independent of any existing private installation and uses the ID chatgpt-inbox-community. A general public relay service, hosted database policy and production service guarantee are not part of this release.

README file from

Github

ChatGPT Inbox Community

Create Markdown notes in your current Obsidian vault from ChatGPT or another compatible MCP client. In Advanced GitHub mode, optional permissions also enable version-checked edits, recoverable trash and original file/photo attachments. Choose which folders may receive notes, and check delivery receipts instead of assuming a queued note has arrived.

An independent MIT-licensed project by David Segade. It is not an official Obsidian or OpenAI product.

Choose your setup (iPhone and desktop)

Start here: Install ChatGPT Inbox Community in Obsidian and choose the mode that matches your needs. Installing the plugin does not automatically create a hosted relay or a custom ChatGPT connector.

  • Lite — simplest: Create a note with an obsidian://new link and confirm it in Obsidian. No hosted server or database is required; delivery is user-initiated and there is no remote receipt.
  • Relay — queued notes with delivery confirmation: Requires an independently hosted, trusted HTTPS relay backed by its own PostgreSQL database, plus a compatible ChatGPT/MCP client. The public plugin includes relay source code, not a free public relay service. Follow relay setup; do not reuse a private test relay or its credentials.
  • Advanced GitHub — optional: Requires a repository, a read-only Contents token configured in Obsidian, and a separate writer that creates requests there.

On iPhone: Leave Obsidian open and active when receiving notes, or use Recibir ahora in Relay mode. The Mac can be off. iOS does not deliver relay notes while Obsidian is suspended in the background. A queued receipt is not proof of a saved note; only delivered confirms that Obsidian verified the write.

Existing installations: Upgrading the plugin does not migrate credentials from a different plugin ID. Avoid changing a working relay origin, device secret or OAuth registration unless you intend to reconnect.

Unified 0.5.0 candidate — GitHub extensions

This candidate consolidates the private receiver features into the public plugin ID chatgpt-inbox-community. It is not a production release until published and physically accepted on iPhone. Existing Relay and Lite modes remain create-only; their servers and credentials are unchanged.

In Advanced GitHub, two separate switches authorize Permitir edición y papelera and Permitir fotos y archivos. Both default off for existing users. Folder scope is still checked before reads and writes, including after asynchronous downloads. The selected GitHub secret identifier is remembered locally per device; the credential stays in SecretStorage. If SecretStorage becomes available after the initial layout, foreground checks recover automatically without opening settings.

  • Edit: version 2 requests require the SHA-256 of the exact previous text. Changed notes produce a conflict. An atomic comparison protects the final write; the previous version is kept under .trash/chatgpt-inbox/update/.
  • Trash: version 2 requests move a matching note to .trash/chatgpt-inbox/trash/. No permanent deletion is performed. Restaurar copia in the inbox restores without overwriting an existing note.
  • Attachments: version 3 requests download original binary blobs from the configured GitHub repository, verify their complete SHA-256 and size, and create files without overwriting different content. A request can carry up to 32 files and 20 MiB total, with an optional linked Markdown note. Formats are preserved; not every format can be previewed by Obsidian. Files are never executed or extracted.
  • Receipts: GitHub results are local (operationLedger and attachmentLedger) and visible in the inbox. A commit is an accepted request, not proof of mobile delivery. The receiver still uses Contents: Read-only; no vault content or receipt is uploaded to GitHub automatically.

See extended request schemas. Files and note content intentionally sent through GitHub remain in that repository's history; use a private repository and include only authorized content.

Do not run two receivers on the same queue. For migration from the private chatgpt-inbox ID, retain a local backup, preserve the existing ledger/history and selected secret identifier, set the configured repository/branch, and enable the new permissions only if requested. Disable the old receiver, then enable Community and verify version, one note, an edit/conflict, trash/restore and image/file integrity on the actual iPhone. Copying settings does not transfer the device credential. Do not remove the backup until mobile acceptance is complete.

Requirements and connection options

Obsidian 1.14.5 or later. The plugin is built for desktop and mobile, without Node.js or Electron dependencies in its installable bundle. Obsidian must be open and active to receive notes; iOS background delivery is not supported. The Mac does not need to be on when the receiving plugin is running on the iPhone.

Mode Requirements Delivery
Relay A trusted HTTPS relay, and a ChatGPT account/client allowed to use custom MCP write tools Queue and verified delivery receipts
Lite An obsidian://new link opened by the user One tap; no remote delivery receipt
Advanced GitHub A repository and a fine-grained, read-only Contents token in Obsidian; a separate writer able to create requests in that repository Receive JSON requests while Obsidian is active

No public relay is included or configured. For Relay mode, use an operator you trust or host the included server yourself. Hosting and database services may cost money. Your ChatGPT plan, client and workspace policies determine whether custom MCP write tools are available; paying for a plan alone does not prove access. No OpenAI API key is required. Custom MCP setup documentation.

Installation

The plugin is listed in the Obsidian Community directory. Search for ChatGPT Inbox Community in Community plugins, or open https://community.obsidian.md/plugins/chatgpt-inbox-community . It has not been manually reviewed by Obsidian staff.

For a candidate build, install it manually in a disposable test vault:

  1. Download the individual main.js, manifest.json and styles.css assets from the GitHub release. Source archives alone are not installable assets.
  2. Place them in .obsidian/plugins/chatgpt-inbox-community/ in that vault (or the corresponding folder under its custom configuration directory).
  3. Enable community plugins and ChatGPT Inbox Community in Obsidian settings.
  4. Open Configure step by step / Configurar paso a paso in the plugin's settings. The current setup interface uses Spanish labels.

This plugin has its own ID and settings. It does not import credentials or replace another ChatGPT Inbox installation. On iPhone, install or sync the plugin files using your normal vault setup, then configure its secret on the iPhone itself. Copying data.json from another device does not transfer its secret.

Connect a relay

An operator prepares the server once: see relay setup. Use a dedicated database and a relay privacy policy you can inspect.

  1. In Configurar paso a paso, select the allowed folders in step 2. For a first test, authorize only ChatGPT Inbox, and use that as the default destination.
  2. Return to step 1, choose Relay beta, and enter its HTTPS origin without a path, for example https://relay.example. Use a distinct secret identifier on each device.
  3. Select Obtener código. The single-use pairing code is valid for five minutes. The device credential is stored locally in Obsidian SecretStorage.
  4. In ChatGPT web, add or open your custom MCP connection. Its URL must be https://relay.example/mcp, with OAuth. Select Connect / Conectar, and paste the code only into the authorization page of the relay you selected, not into the chat. An existing connection such as OB-ChatGPT is just the name chosen by its owner; other users create their own connection.
  5. Return to step 3 in Obsidian and select Comprobar y activar. Keep Obsidian open.
  6. Select the connector in a ChatGPT conversation and ask it to list the folders, create a test note and check its receipt. If it is queued, open Obsidian and select Recibir ahora, then check again. Only delivered confirms a verified write.

The relay exposes listar_carpetas, crear_nota and consultar_estado. Notes are create-only; an existing unrelated file produces a conflict instead of being overwritten. Reusing the same retry key with the same content returns the same receipt. A revoked folder blocks the queued note until permission is restored or it expires.

Authorization and mobile use

Access tokens last up to one hour. The 0.4.1 relay issues rotating refresh tokens so a compatible OAuth client can renew access without another pairing every hour. Each refresh credential can be used once; replay revokes that client grant. A connection expires after seven days without refreshing, after thirty days in total, or at the rotation safety limit. Revoking the device in Obsidian invalidates its access and refresh credentials immediately.

Connections created by an older relay do not gain a refresh token automatically: authorize once again after upgrading. Automatic renewal also depends on the client; it has been exercised through protocol tests, not by waiting for every supported ChatGPT app to renew on a real device. Registered OAuth clients are retained so reconnecting does not require creating a new ChatGPT connector.

Reception checks at most once per configured interval (minimum 60 seconds; default 120), while Obsidian is active. Open Recibir ahora for an immediate check. Vault synchronization is a separate service and is not supplied by this plugin.

Reception and connection checks in 0.4.4

The setup assistant checks both the authorized default destination and the device connection before activating reception. A current relay also reports whether client authorization is complete. Choosing a folder does not grant access to another folder merely because it is the default destination.

The inbox distinguishes a verified local note waiting for its relay receipt from a confirmed delivery, a conflict and a blocked request. A failed receipt is retried with the existing identity; it does not create another note. Connection status and the last successful check do not by themselves confirm that a particular note arrived.

While Obsidian is active, transient failures retry after 1, 2, 4, 8 and at most 15 minutes. A manual receive can retry sooner, but must respect server rate limits. Requests have a 20-second deadline. Moving into the background releases outstanding waits; a late response cannot resume an obsolete receiver. Returning to Obsidian checks again when appropriate. These controls do not enable iOS background delivery.

After activating Relay mode, Crear nota de prueba y verificar creates a synthetic note inside the authorized default folder and queries its receipt. Its retry key is saved before contacting the relay, so interruptions or restarts reuse the same request. A delivered test also requires the expected local note and its identity. The test checks relay → Obsidian; send a note from your actual client to check that client's MCP tool access too. Running another test after confirmation deliberately creates another synthetic note. A new pairing also starts a new test sequence because the previous device grant has been revoked.

The test button requires the operator to update the separate relay to 0.4.4. Older relays continue normal reception and show an explanatory message for this optional feature. Updating the Obsidian plugin does not deploy or update a hosted relay.

Ver diagnóstico shows a report for review and optional native copy. It contains versions, transport, status, check timestamps and aggregate counts; it omits notes, paths, folder/vault names, server/repository addresses, request IDs, pairing codes and credentials. It is never uploaded automatically. See mobile acceptance for the distinction between automated, desktop and physical-iPhone evidence.

Lite and GitHub

Lite produces an obsidian://new link locally. Open the link deliberately; it does not provide a remote receipt. Anyone who sees the link can read its encoded content. Long links or title conflicts should be checked before use.

Advanced GitHub mode reads request JSON files using GET requests to the repository you configure. Obsidian uses a fine-grained Contents read-only token. A separate writer must create those requests: do not assume that a ChatGPT GitHub connection can write. The wizard supplies the required request format and allowed folders. Paths are relative to the vault, without its name. Do not put private content in a public repository.

Data and privacy

Relay mode sends authorized folder names, connection activity and delivery states to the chosen operator. The new note's title and content pass through the relay. HTTPS protects transport; the operator can see the plaintext. Existing vault notes are not uploaded by the receiver. Identity lookup and content verification stay local and respect current folder permissions. Hidden/configuration paths are blocked.

Pending content expires after 24 hours and is removed from the active store at delivery, conflict or expiry. Receipts and retry keys last up to 48 hours from creation. Backups and infrastructure logs have a separate retention policy, supplied by the operator. Credentials use SecretStorage locally and hashes on the relay; note paths, deduplication hashes and the latest 100 history entries are stored locally. No ads, client telemetry, analytics, remote code loading or self-updater are included. See privacy and permissions.

Status and development

Version 0.4.3 is published in the Community directory and its automated review passed. Version 0.4.4 is the reliability candidate in this source tree until its release is published and scanned. Directory listing does not imply manual approval. Desktop acceptance was performed on Obsidian 1.14.5. A user reported the configured iPhone flow working; the exact iOS/Obsidian version and the full physical-device acceptance matrix remain to be recorded. See acceptance evidence and the submission checklist.

Build from source with Node.js 24:

npm ci
npm run verify
npm run package:community -- /absolute/new/staging-folder

npm run test:postgres additionally needs a new disposable local database and a restricted test role, as described in relay setup. Node.js is required for building and operating the separate relay, not for running the Obsidian plugin.

License

MIT.