Skip to content

armgit / Orkas

Public Imported from GitHub
0

Orkas is an open-source (MIT), local-first AI team for your desktop: a Commander turns your goal into to-dos and coordinates 16 built-in specialist agents plus Claude Code, Codex, OpenCode, OpenClaw and Hermes, with projects, scheduled automations and connectors. Free app for macOS & Windows; built-in models or your own keys.

Pending-queue panel makes room for the workspace + plan-rail chips on the shoulders

claw23eb5ea19d82e
diff --git a/src/renderer/modules/conversation.js b/src/renderer/modules/conversation.js
index 67fccd93..c2121634 100644
--- a/src/renderer/modules/conversation.js
+++ b/src/renderer/modules/conversation.js
@@ -1798,8 +1798,15 @@ function _makeConvChatController(cid) {
},
onDone(_msgEl, id) {
// Unconditional cleanup — safe even if polling already resolved.
+ // `_finishStreamingMsg` synchronously drains the next queued
+ // message (via `_dispatchNextQueued` → new `ctrl.send`), which
+ // appends the user bubble + RE-ARMS the scroll-pin spacer for the
+ // new turn. We must NOT call `_setChatScrollOffset(false)` here —
+ // the controller finally block already removed the OLD spacer
+ // before invoking us, so a second removal would strip the spacer
+ // the new turn just added and the queued user message would render
+ // off-screen until later layout shifts pushed it into view.
_finishStreamingMsg(id);
- _setChatScrollOffset(false);
// Only drop the map entry if it still refers to *this* controller.
// On abort we dispatch the next queued message synchronously from
// `onAbort`, which assigns a new controller into `_convChatCtrls`
diff --git a/src/renderer/modules/plan-rail.js b/src/renderer/modules/plan-rail.js
index a84849fb..b2a243cd 100644
--- a/src/renderer/modules/plan-rail.js
+++ b/src/renderer/modules/plan-rail.js
@@ -85,13 +85,21 @@ function _render(plan) {
const body = document.getElementById('plan-rail-body');
const progress = document.getElementById('plan-rail-progress');
if (!root || !body || !progress) return;
+ // Mirror visibility onto the wrapper so .chat-queue can reserve left-side
+ // room for the rail's pill chip (chip floats above the input bubble's
+ // left shoulder; without this the queue panel's bottom-left would
+ // overlap the chip — symmetric to the workspace-chip reservation on the
+ // right).
+ const wrap = root.closest('.chat-input-wrapper');
if (!plan || !Array.isArray(plan.steps) || plan.steps.length === 0) {
root.style.display = 'none';
body.innerHTML = '';
progress.textContent = '';
+ if (wrap) wrap.classList.remove('has-plan-rail');
return;
}
root.style.display = '';
+ if (wrap) wrap.classList.add('has-plan-rail');
progress.textContent = _buildProgressText(plan);
body.innerHTML = plan.steps.map(_buildStepHtml).join('');
}
diff --git a/src/renderer/style.css b/src/renderer/style.css
index 443051de..85b25d5f 100644
--- a/src/renderer/style.css
+++ b/src/renderer/style.css
@@ -1714,11 +1714,18 @@ body.model-not-configured .main-content { flex-direction: column; }
.chat-send-btn.streaming .send-icon { display: none; }
.chat-send-btn.streaming .stop-icon { display: block; }
-/* Queue panel above the input area */
+/* Queue panel above the input area.
+ Aligned with .chat-input-area's centered 80% layout BUT with the right
+ edge shrunken to clear the workspace chip floating above the input
+ bubble (chip is anchored to input-area's right shoulder, up to ~218px
+ wide; without this it overlaps the queue's bottom-right corner). The
+ shared `--ws-chip-reserve` lives next to `.chat-input-overlay` so any
+ future chip-width tweak only needs one site update. */
.chat-queue {
pointer-events: auto;
- max-width: 80%;
- margin: 0 auto 8px;
+ width: 80%;
+ max-width: max(160px, calc(80% - var(--ws-chip-reserve, 232px)));
+ margin: 0 0 8px 10%;
background: rgba(255, 255, 255, 0.96);
backdrop-filter: blur(6px);
border: 1px solid var(--border);
@@ -1727,11 +1734,27 @@ body.model-not-configured .main-content { flex-direction: column; }
box-shadow: 0 6px 20px rgba(15, 23, 42, 0.08);
}
+/* Plan-rail pill chip floats above the input bubble's LEFT shoulder, the
+ mirror of the workspace chip on the right. When a plan exists,
+ plan-rail.js stamps `has-plan-rail` on .chat-input-wrapper; reserve
+ ~188px on the queue's left so the chip clears the queue's bottom-left.
+ Symmetric to the right-side workspace reserve above. */
+.chat-input-wrapper.has-plan-rail .chat-queue {
+ margin-left: calc(10% + var(--plan-rail-reserve, 188px));
+ max-width: max(
+ 120px,
+ calc(80% - var(--ws-chip-reserve, 232px) - var(--plan-rail-reserve, 188px))
+ );
+}
+
/* Narrower panels (skill / agent edit) don't have the 80%-centered shape
of the main chat input; let the queue span the full panel width so it
- aligns with the message list / input above. */
+ aligns with the message list / input above. They also have no
+ workspace chip floating above the input area, so no right-side
+ reservation is needed. */
.skills-chat-col .chat-queue,
.agents-chat-col .chat-queue {
+ width: auto;
max-width: none;
margin: 0 12px 8px;
}