Repository navigation
Repository skeleton for the Filesystems WG - #1
Merged
Merged
Conversation
README, CONTRIBUTING, AGENTS/CLAUDE, SECURITY and CODEOWNERS following ext-skills; docs/ for open questions (from the charter), decision log, related work and implementations; a python/sdk placeholder package with CI following experimental-ext-interceptors; and a conformance/ folder. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
… to SDK extension points Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… was dropped The File Uploads and Filesystems charter merge (#3389) was abandoned on 2026-10-11, so the references to the Files Working Group, its charter PR and its three workstreams now point at the Filesystems WG charter and the File Uploads WG instead. Scope text follows the Filesystems charter (create, update, delete, stat, concurrency, change notification and caching).
jayzuccarelli
changed the title
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ments Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
olaservo
added a commit
that referenced
this pull request
Nov 4, 2026
- Open questions cite PS items and the trimmed open-questions.md instead of old #1-#6 numbering - List PS4.4, PS4.5 (permission/read-only/quota), PS5.5, PS6.3 as open, and note the PS6.4 departure - Raise required ifMatch on delete and contents.uri redundancy as open questions - Add lastModified to create/update examples, as the Interactions section requires Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
olaservo
added a commit
that referenced
this pull request
Nov 4, 2026
Fast follow to #1. Docs only. `docs/problem-statements.md` (#3) is now the source of truth for scope, open questions, and SEP status, so the skeleton docs link to it instead of restating it: - **README**: scope covers listing, search/glob, bulk/partial reads, writes, and `stat` (per PS1–6), and links the problem statements. - **open-questions.md**: keeps only cross-cutting questions (SEP-2571/2532 disposition, uploads vs. writes, Skills `resources/directory/read`) and links the PS items; per-statement questions live in the problem statements. - **related-work.md**: drops the SEP table, which had already drifted (SEP-2631 listed as Draft; it closed 2026-10-14), and points to PS "Related proposals". Adds the File Uploads extension. - **use-cases.md**: links the running example and PS1–3 for the two cases they already cover; memory-server and base64 cases unchanged. AI disclosure: drafted with Claude Code; reviewed by me. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
DanielTemesgen
pushed a commit
that referenced
this pull request
Nov 11, 2026
…sion-based concurrency (#2) Builds on #1 (the repository skeleton); the first commit here is that branch, so review from the strawman commits on, or after #1 merges. Strawman for the Resource operations SEP in the [Filesystems WG charter](https://modelcontextprotocol.io/community/working-groups/filesystems), to give the group something concrete to review and change. - `docs/proposals/resource-operations.md`: `resources/stat`, `resources/create` (create-if-absent), `resources/update` (requires `ifMatch`), `resources/delete` (optional `ifMatch`); an opaque `version` as the concurrency token; typed errors (provisional `-32010` precondition failed with `currentVersion`, `-32011` not supported; `-32602` for not found, matching `resources/read`). Listing reuses SEP-2640's `resources/directory/read` unchanged. Search, glob, bulk, and range are deferred. - `docs/decisions.md`: 2026-10-09 entry, Status: Proposed. - `python/sdk`: prototype on the SDK's `Extension`/`MethodBinding` API (no SDK changes), pluggable store plus in-memory store, client helpers, tests including the lost-update case from `use-cases.md`. - `conformance/`: two implementation-independent conflict scenarios. The proposal lists five gaps in the Python SDK's extension points as feedback for SEP-3371 (no subscription bus access from extension handlers, no metadata on change events, no hook into `resources/read`, one method across two extensions, legacy wire). Vocabulary (`version`, change-set entries) follows Kryspin Ziemski's working document shared in #filesystem-wg. AI disclosure: drafted with Claude Code; I reviewed the spec and code and ran the tests locally. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Kryspin Ziemski <321453+kziemski@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Following up on the #filesystem-wg thread (cc @olaservo): a skeleton like ext-skills and experimental-ext-interceptors, so proposals have somewhere to land.
filesystems-wg)docs/: problem statement and use cases, open questions taken from the charter, an empty decision log with the ADR-lite template, related work (including SEP-2133 and SEP-3371), implementationspython/sdk/: placeholdermcp-ext-filesystemspackage on MCP Python SDK v2, meant to plug in through the SDK's extension points (SEP-3371), with CI (ruff, mypy, pytest on 3.10 to 3.13)conformance/: placeholder for scenariosNo decisions or spec text. A Resource operations strawman follows as its own PR.
AI disclosure: drafted with Claude Code; I reviewed every file and ran the Python checks locally.