Ironclad / Ironclad/rivet

[Feature]: Register plugins with Rivet core chat-related facilities

Open
#192 2 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
TypeScript
Stars
4.7k
Forks
388
PR merge metrics
No merged PRs in 30d

Description

### Feature Request

Current implementation of Rivet assumes that only nodes of type 'chat' and to some extent 'chatAntropic' are integrated in various editor components, such as `ChatViewer`.
I'd suggest adding an extension point allowing for plugins to register for such services.
I'm also willing to implement it.

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Research direction

Start by tracing how nodes of type `chat` and `chatAntropic` are integrated into editor components such as `ChatViewer`. Identify the existing Rivet core chat-related facilities and determine the extension-point design needed for plugins to register with them. Done means plugins can register for those services without relying on built-in node types; no specific test file is named.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
ai, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.