redhat-developer / redhat-developer/abbenay
feat(grpc): implement stubbed proto RPCs (WatchSessions, ReplaySession, ForkSession, Export/ImportSession, ExecuteTool)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12
- Forks
- 7
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 3
Description
Summary
The following RPCs are defined in service.proto but return UNIMPLEMENTED in abbenay-service.ts:
| RPC | Purpose |
|---|---|
WatchSessions |
Server-stream of session lifecycle events (handler closes stream immediately) |
ReplaySession |
Replay a session's message history |
ForkSession |
Create a new session branched from an existing one |
ExportSession |
Export session as portable JSON |
ImportSession |
Import session from portable JSON |
ExecuteTool |
Execute a tool directly (outside of a chat context) |
These should either be implemented or removed from the proto to avoid confusion for client implementors.
Proposal
Prioritize based on client needs:
- High:
WatchSessions— useful for real-time UI updates in VS Code - Medium:
ForkSession,ExportSession,ImportSession— session management features - Medium:
ExecuteTool— useful for tool testing/debugging UIs - Low:
ReplaySession— niche use case
If any are not planned, mark them as reserved in the proto with a comment explaining they are not yet available.
Context
Identified during gRPC config parity audit in #32.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the RPC definitions in service.proto with their handlers in abbenay-service.ts, then review the gRPC config parity audit in #32. Determine the intended scope for each listed RPC and whether it should be implemented or reserved. Done requires an agreed outcome for all six RPCs, including corresponding behavior or explicit proto reservations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100