Skip to content
Discussion options

You must be logged in to vote

The reusable R-side integration now lives in the bundled sess package. #1764 establishes explicit endpoint/discovery metadata and stable session IDs, so another editor could implement a client for that protocol and use sess::connect(endpoint = ...).

That still requires an editor-side implementation of the session handshake, JSON-RPC handlers, and the viewer/editor requests it intends to support. Installing sess or languageserver alone does not provide a ready-made Neovim/coc integration.

This answers the architectural part of the question; I have not verified a supported non-VS Code client.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by eitsupi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #1470 on October 10, 2026 14:58.