[self-built FEATURE - is it future proof?]
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
<img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/e0371a05-ed77-473b-b4bc-20d1128076d3" />
I made a self-built feature for Claude (Claude Remote Control from an opsbox developing Payload app/site factory and app hosting on Kubernetes with GitOps):
as you see on the attached screenshot, I made 5 permanent sessions for each purpose, 1 for fixing bugs and issues (Fix), one for asking questions, read-only (Info), one for dropping new dev tasks (Drop), one for acking, when Claude wants me to choose or do terminal work (Ack), and finally the "original" session called (Queue), where is the claude narration and monologue of everything that is happening.
The question is if this is the direction where Claude is being built or going? And if this is the right and most effective way to work with Claude?
The issue was that:
1: - A single thread made me wait a lot, because we cannot add queued messages anytime, we can but they will not be ingested for real until the session is busy, for example if we leave that UI interface, the queued message will be gone, it will not enter the conversation (or this might be a bug, if not intended).
2: - Sessions want to have a dedicated purpose each, and I needed to mandate to keep the monologue in the Queue session, because the other sessions are for other purposes, so scoping the sessions is what happened - I have not seen this deafult feature in Claude, am I missing anything? So I mandated it for Claude to set itself up for this "feature". Because Claude apparently can route what it has to say to different sessions, and this was the idea. Also, it can ask what want to ask in different sessions, within the whole dev work which is one in fact. This was the other idea that I asked Claude to implement for itself.
So the question is: this kind of prompt-mandated sessions scoping, and Calude replies and questions routing - is this future proof, and is Claude going this way architecturally, or this is rather a hack, and Claude already have or will have other features for this purpose?
Just so I wouldn't invest too much setup for this, if the Claude engineers intended it otherwise for the future.
Any feedbacks on this much appreciated.
Proposed Solution
Eventually making this an offical feature, if it doesn't exist yet - or I just missed it out?
Alternative Solutions
_No response_
Priority
High - Significant impact on productivity
Feature Category
Configuration and settings
Use Case Example
Additional Context
_No response_