c2a6889567bead1704cfabd36da0dd281a2a651c
14 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Eyejoker
|
ea323cc787 |
Overhaul dashboard UX (two-pane rooms, live turn persistence, react-markdown) (#42)
* Overhaul dashboard UX with two-pane rooms and live turn persistence - Two-pane room board (Discord-style list + detail) with sender role colors, inbox attention badges, and per-role left-border sectioning - Settings page: nickname + language extracted to /#/settings; sidebar freed up for mini stats (rooms, queue, inbox) and nav badges - react-markdown + remark-gfm for message body (tables, code, links, proper line breaks); unified timeline merges outputs and human messages - Live turn elapsed counter ticks every second; paused state preserved across service restarts via new progress_text column on paired_turns (migration 015) so in-flight context survives reboots - Batched /api/rooms-timeline endpoint with server-side stale-while- revalidate cache + gzip; cold ~3s -> warm ~10ms - Optimistic UI for outgoing messages with rollback on failure; nickname propagated to sender_name on send - Density sweep: tighter paddings, radii, font sizes; tokens align across panel/card/sidebar/timeline Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Strip redundant LIVE/intent/state labels from turn header The left dot already signals LIVE and the role chip already shows the turn role; the standalone LIVE label, intentKind em, and state pill were repeating that information. Keep only role chip, time, elapsed, and a "중단됨" label when paused. Also picks up Prettier-formatted long lines in i18n and backend files left over from the previous commit. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Convert sidebar to lucide-react icon rail and fix optimistic UI - Replace 168px text-label sidebar with 56px flush-left icon rail (lucide-react icons: Gauge/Inbox/Activity/MessageSquare/Clock/Settings) Discord/Slack pattern: rail against left edge, no centered shell margin - Optimistic UI now survives polling: pending messages tracked in a separate state and merged into the timeline render; an effect prunes pending entries once the server snapshot confirms them by content match - LIVE elapsed counter shows seconds at all granularities (formatLiveElapsed uses m+s/h+m+s instead of dropping seconds after 60s) - Refresh button shows spin animation while busy Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Make Rooms the default landing view Rooms is the primary surface (chat-style live agent flow), so reorder nav (Rooms first) and switch DEFAULT_VIEW from inbox to rooms. The topbar fallback label also changes from 'usage' to 'rooms'. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Submit room message on Enter, allow Shift+Enter for newline IME composition (event.nativeEvent.isComposing) is excluded so that mid-Hangul Enter does not trigger send. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Viewport-lock rooms view to remove double scroll The rooms view now fills the viewport (height: 100vh - topbar) with list and detail each scrolling in their own column. The page itself no longer scrolls when the detail thread grows long, so the wheel scrolls whichever column the cursor is over. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Flatten rooms view, single-line compose with icon send button Drop nested card chrome on rooms view: outer panel now has no padding, border, or background so the rail / list / detail sit flush against the page. Internal panes (rooms-list, rooms-detail) lose their own borders and rely on a single divider line for separation. Compose textarea is single-row by default (rows=1) and grows up to ~5 lines; the send button is icon-only (Send from lucide-react), fixed 36x36, pinned to the bottom of the detail pane. The redundant '메시지' h4 and the 세부 fold are removed — the room title in the header already establishes context. Detail pane is now a flex column where only the timeline scrolls; the head sticks at top and the compose pins at bottom (messenger pattern), so the input is always reachable. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Fix rooms layout: viewport lock, restore panel tone, ensure thread scrolls - Lock body to viewport height (overflow:hidden) only when rooms view is active, via body:has(.view-stack.view-rooms). Section nav becomes static so the layout fits exactly in the viewport instead of being clipped under the sticky header. - Restore subtle panel background and border on .rooms-list and .rooms-detail so chat content has tonal contrast against the page bg (pure black was unreadable). Outer panel chrome stays flat. - Make the thread section the only flex:1 child of the pinned card so it actually scrolls when content overflows; everything else (head, meta, current turn, watcher fold, compose) stays flex:none. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Make rooms-detail itself scroll with sticky head and compose Drop the brittle flex-column-with-1fr-child setup; just let .rooms-detail be overflow-y:auto and pin .room-card-head to top and .room-compose-section to bottom via position:sticky. The head and compose stay visible while the thread between them scrolls naturally. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Match compose-section background to panel The sticky compose bar was using var(--bg) (near-black) which jarred against the surrounding panel tone. Use var(--panel) so it sits continuously with the room detail. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Fix compose full-width and hide internal IPC payloads - The compose section's full-width grid was being clobbered by the later .room-section { display: grid } rule (same specificity, source order won). Bump specificity to .room-section.room-compose-section with display: block so the inner form/textarea fills the panel. - Filter out internal protocol payloads from the timeline: isInternalProtocolPayload() detects {"author":..."recipient":...} shaped agent IPC messages and excludes them from humanMessages and outputEntries. These are routing metadata, not human-readable chat. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Tighten rooms width: explicit 100% on detail/card, responsive list - Make rooms-list responsive (clamp(180px, 16vw, 240px)) so on smaller screens the chat area gets more room - Add explicit width: 100% to rooms-twopane, rooms-detail, and the pinned room-card-v2 so nothing collapses to content-size Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Remove timeline left indent and broaden IPC payload filter - Drop the 3px colored left border + 12px left padding on each timeline item; messages were starting 29px from the panel edge (3 border + 12 item padding + 14 thread padding). Role colors are already conveyed by the role chip, so the border is redundant. - Tighten thread-section padding from 14px to 12px to match compose. - Broaden isInternalProtocolPayload to also catch <sub-agent-prompt>, <tool-call>, <internal> wrapped payloads — these were leaking into the visible thread when the agent emitted them as message content. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Restore role color borders and tighten left padding - Bring back the role-colored left border on timeline items (2px now, was 3px) so owner/reviewer/arbiter/human are visually distinct - Tighten left-side spacing across the chat panel: thread section padding-left 12 -> 4, item padding-left 12 -> 8, card head padding-left 14 -> 8, compose-section padding-left 12 -> 4. Content now starts ~10px from the detail panel's inner edge instead of ~30px Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Unclamp output text in unified timeline + add measure debug toggle - The legacy .room-output-item p / .room-message-item p / .room-latest-output p rules used -webkit-line-clamp:2/4 to truncate previews. The unified timeline doesn't use those classes so it shouldn't be clamped, but add a defensive override on .room-timeline-body .parsed-body that unclamps and clears max-height in case any sibling rule leaks in. - Add ?debug=1 (outline panels) and ?measure=1 (overlay container x/w in viewport coords) toggles via App.tsx so we can diagnose layout issues without npm-installing devtools. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Tighten rooms layout left/right margins Drop view-panel and section-nav left margin from 12px to 8px. Removes the visible empty band between icon-rail and rooms-list (was 12px, now 8px). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Remove internal left padding in rooms-detail panel The detail panel had 4-8px of left padding inside the thread and compose sections, leaving an empty band on the left. Drop padding-left to 0 on .room-thread-section and .room-compose-section. Timeline items keep their own 8px padding-left (for the role border + text gap), and the textarea inherits the same flush-left starting position as messages — they align vertically now. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Fix 26px left empty band: zero out .room-expanded padding in pinned mode Root cause located via pixel scan + DOM dump: the legacy .room-expanded wrapper (used by the click-to-expand layout) has padding: 14px 0 4px 26px to align expanded content with the head's pulse-dot column. In the pinned twopane layout it was leaving a 26px empty band between the panel border and the chat content. Override .room-expanded inside .room-card-v2.is-pinned to zero padding/margin/border-top/gap, so thread-section and compose-section align flush at the panel's inner left edge. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Add Playwright + dash-inspect helper script Playwright (chromium) is installed so future layout debugging can use real DOM/computed-style queries instead of pixel scans on screenshots. Helper commands: bun scripts/dash-inspect.ts shot [route] bun scripts/dash-inspect.ts measure '<selector>' bun scripts/dash-inspect.ts eval '<expr>' bun scripts/dash-inspect.ts dom '<selector>' bun scripts/dash-inspect.ts click '<selector>' Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Auto-scroll chat to bottom on send and on new messages - When the user sends a message, scroll the rooms-detail panel to the very bottom over 4 frames (covers the post-render layout settle). - Add a near-bottom tracker: a ref flips false when the user scrolls more than 80px from the bottom, true otherwise. The auto-follow effect (triggered when messages/outputs/pending counts change) only scrolls if the user was already near the bottom — so reading scrollback doesn't get yanked. - Initial room selection and any new content added while at-bottom always shows the latest message. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Add Settings page: model role config + multi-account management Backend: - src/settings-store.ts: filesystem reader for Claude (~/.claude, ~/.claude-accounts/N) and Codex (~/.codex, ~/.codex-accounts/N) account directories. Returns safe metadata only (expiresAt, scopes, subscriptionType, planType, accountId from JWT) — never raw tokens. Atomic .env writer for OWNER/REVIEWER/ARBITER MODEL/EFFORT pairs. Account directory deletion (refuses index 0). Claude account add via pasted OAuth JWT (decodes exp/sub from payload, writes new ~/.claude-accounts/N/.credentials.json). - src/web-dashboard-server.ts: new endpoints GET /api/settings/accounts GET /api/settings/models PUT /api/settings/models (PATCH alias) POST /api/settings/accounts/claude (body: { token }) DELETE /api/settings/accounts/{provider}/{index} Frontend: - apps/dashboard/src/api.ts: typed clients for the new endpoints. - apps/dashboard/src/App.tsx: SettingsPanel split into 일반 / 모델 / 계정. Model section: editable owner/reviewer/arbiter model+effort fields with dirty tracking and a save button. Account section: per-provider list with delete buttons (default index 0 protected) and a token-paste field for adding a Claude account. Both sections expose a "스택 재시작" button that calls the existing /api/services/stack/actions endpoint with a confirmation prompt — changes only take effect after restart. UX scope: phase B (model edit + account delete) + phase D (account add via paste) per the recommendation; full OAuth flow not included. Restart is gated behind a confirm() since it kills running agents. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Format: Prettier follow-up on settings PR Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Show cron / external-trigger messages inline (separate from CI watcher) trusted_external_bot messages (Sentry Cron, GitHub webhook triggers, etc.) were lumped into the CI-watcher fold and hidden by default. Split them: WATCHER_RE now only matches actual CI status messages (Build/Deploy/Lint/Release/[CI]/[Watcher]/GitHub Actions on bot kind), so the watcher fold stays focused on CI noise. trusted_external_bot messages now get rendered inline in the unified timeline as cronMessages (sourceKind preserved). senderRoleClass returns 'role-cron' for senders matching cron/sentry/webhook so the chip and left border show in muted gray to visually distinguish from agent and human messages. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Live progress fallback: scan TASK_STATUS messages for current turn only When paired_turns.progress_text is empty (codex runner doesn't always populate it in time), fall back to scanning the room's messages table for ones starting with the TASK_STATUS_MESSAGE_PREFIX (the invisible 3-char prefix used on Discord live-edit messages). Strip the prefix and the trailing elapsed indicator (e.g. "\n\n12초"), then render in the LIVE timeline entry. Filters: - timestamp must be >= turn.createdAt (don't show pre-turn history) - sender role must match the current turn's role (don't show a stale reviewer status when owner is now speaking) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Server fallback: derive live progressText from messages when column empty Keep paired_turns.progress_text as the primary source (populated by recordTurnProgress in MessageTurnController). When the column is empty on an active turn — happens for codex turns where the controller path isn't fully wired, or any path where ingestion lags — scan the messages table for the most recent TASK_STATUS_MESSAGE_PREFIX-prefixed message that belongs to the current turn (sender role match + timestamp >= turn.createdAt) and use that as progressText. This makes the dashboard converge with Discord without requiring the column to be reliably written: if Discord shows a live edit, the ingest pipeline writes it to messages, and we surface it. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Poll room timelines every 1.5s on rooms view (was every 15s) The rooms-detail thread was reusing the 15s overview refresh tick, which made the chat lag noticeably behind Discord. Add a dedicated setInterval(1500ms) fetch on the rooms view (cleared when leaving), with an in-flight guard so overlapping ticks don't pile up. Backend already has a 2s stale-while-revalidate cache so this stays cheap. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Real-time rooms updates via Server-Sent Events Backend: GET /api/stream emits text/event-stream with 'rooms-timeline' events whenever the server's roomsTimelineCache rebuilds (key change). A 1.5s tick checks the cache; if builtAt advanced, push the new JSON, otherwise send a SSE comment heartbeat ': ping ts\n\n' to keep proxies from idle-closing the connection. AbortSignal handler closes the ReadableStream when the client disconnects. Frontend: replace setInterval(1500ms) on rooms view with EventSource. Initial fetch primes the data so first paint isn't blank, then SSE takes over for instant updates. EventSource auto-reconnects on disconnect; while it's flapping, a 2s polling fallback runs so data keeps flowing. When SSE recovers (next 'rooms-timeline' event) the polling fallback is cleared. Latency: previously 0–1.5s polling lag; now ~tick latency (50–150ms) once cache rebuilds. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Add breathing room between timeline header and body Increase room-timeline-item gap from 2px to 6px so the role chip / timestamp line has visible breathing room above the parsed body — header → body relationship reads more clearly. Bump vertical padding from 6px to 8px and item separator from 1px to 2px to match. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Hide the 2px processing bar in pinned twopane to free role-color borders .room-card-v2.status-processing::before draws a 2px green bar at the card's left edge. In pinned twopane mode it sits right on top of each timeline item's role-colored left border (owner blue / reviewer orange / arbiter green / human yellow), masking them. The header's pulse dot already conveys "processing", so suppress the bar in pinned mode and let the role colors show through. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Polish room compose: tighter pill input + override global button min-height The 48px button min-height global rule was forcing the compose grid track to 48px, pushing the textarea content visibly down inside the pill. Adding min-height: 0 on the compose button lets the track collapse to ~29px so the placeholder lines up with the send button vertically. Also slimmed paddings (form 3px vert, textarea 4px vert) and added bottom breathing room on the compose section (8px → 14px) at user request. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Format styles.css to multi-line transition values Prettier 3.8.1 prefers multi-line transition shorthand. CI was failing format:check on these single-line transitions in the room-compose rules. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com> |
||
|
ejclaw
|
e036521054 |
fix: salvage EJClaw runtime hardening
- add dist freshness guard to deploy flow - preserve message source provenance for IPC injection - harden Codex usage fallback and workspace package manager detection - document owner branch return protocol |
||
|
Eyejoker
|
648457d717 |
chore: remove nanoclaw legacy skills and scripts
Remove 9 inherited skills (Qodo, update-ejclaw, add-* addons, update-skills) and restart-ejclaw-stack.sh that came from the nanoclaw fork and are no longer used. |
||
|
Eyejoker
|
35ba7cb5ba |
chore: replace all node/npm/tsx references with bun across codebase
- Source: setup/service.ts, runners.ts, agent-runner.ts error messages - Scripts: restart-stack.sh, run-migrations.ts → bun - Bootstrap: setup.sh check_node→check_bun, npm install→bun install - Docs: CLAUDE.md, README.md, all SKILL.md files - Tests: service.test.ts, restart-stack.test.ts expectations updated |
||
|
Eyejoker
|
16d20fe627 |
feat: paired review system overhaul — unified service, configurable agents, silent output removal
- Remove UNIFIED_MODE legacy: single service manages all 3 Discord bots - Add OWNER_AGENT_TYPE / REVIEWER_AGENT_TYPE env vars for configurable agent selection - Fix Discord channel routing: reviewer output goes through correct bot (discord/discord-review) - Fix channel name assignment: explicit names prevent agentTypeFilter collision - Remove silent output suppression system: harness-level protections replace prompt workarounds - Add reviewer approval detection: DONE marker on first line stops ping-pong - Include user's original message in reviewer prompt for context - Fix round_trip_count auto-reset on new user message - Fix session ID conflict: reviewer doesn't reuse owner's session - Fix pending progress text flush in runner on close sentinel - Promote buffered intermediate text to final result when result event has no text - Remove legacy files: .env.codex.example, .env.codex-review.example, migrate-unify.cjs - Update CLAUDE.md: server-side build deployment, unified architecture docs |
||
|
Eyejoker
|
ca578d1627 | feat: add stack restart orchestration | ||
|
Eyejoker
|
d28b6151a8 | chore: rebrand runtime and docs to EJClaw | ||
|
Eyejoker
|
a293a701f4 | fix: restore regressions from discord-only refactor | ||
|
gavrielc
|
5118239cea |
feat: skills as branches, channels as forks
Replace the custom skills engine with standard git operations. Feature skills are now git branches (on upstream or channel forks) applied via `git merge`. Channels are separate fork repos. - Remove skills-engine/ (6,300+ lines), apply/uninstall/rebase scripts - Remove old skill format (add/, modify/, manifest.yaml) from all skills - Remove old CI (skill-drift.yml, skill-pr.yml) - Add merge-forward CI for upstream skill branches - Add fork notification (repository_dispatch to channel forks) - Add marketplace config (.claude/settings.json) - Add /update-skills operational skill - Update /setup and /customize for marketplace plugin install - Add docs/skills-as-branches.md architecture doc Channel forks created: nanoclaw-whatsapp (with 5 skill branches), nanoclaw-telegram, nanoclaw-discord, nanoclaw-slack, nanoclaw-gmail. Upstream retains: skill/ollama-tool, skill/apple-container, skill/compact. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|
gavrielc
|
80cdd23c84 |
chore: remove old /update skill, replaced by /update-nanoclaw
The new /update-nanoclaw skill (PR #217) replaces the old update mechanism. Delete the old skill, update module, CLI scripts, and tests. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|
Gabi Simons
|
11c201088b |
refactor: CI optimization, logging improvements, and codebase formatting (#456)
* fix(db): remove unique constraint on folder to support multi-channel agents * ci: implement automated skill drift detection and self-healing PRs * fix: align registration logic with Gavriel's feedback and fix build/test issues from Daniel Mi * style: conform to prettier standards for CI validation * test: fix branch naming inconsistency in CI (master vs main) * fix(ci): robust module resolution by removing file extensions in scripts * refactor(ci): simplify skill validation by removing redundant combination tests * style: conform skills-engine to prettier, unify logging in index.ts and cleanup unused imports * refactor: extract multi-channel DB changes to separate branch Move channel column, folder suffix logic, and related migrations to feat/multi-channel-db-v2 for independent review. This PR now contains only CI/CD optimizations, Prettier formatting, and logging improvements. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> |
||
|
Gabi Simons
|
29a5dafe01 | refactor: remove deterministic caching system from skills engine (#453) | ||
|
gavrielc
|
1216b5b99c |
feat: add /update skill for pulling upstream changes (#372)
Interactive skill that guides Claude through fetching upstream NanoClaw, previewing changes, merging with customizations, running migrations, and verifying the result. Includes: - SKILL.md with 9-step update flow - fetch-upstream.sh: detects remote, fetches, extracts tracked paths - run-migrations.ts: discovers and runs version-ordered migrations - post-update.ts: clears backup after conflict resolution - update-core.ts: adds --json and --preview-only flags - BASE_INCLUDES moved to constants.ts as single source of truth - 16 new tests covering fetch, migrations, and CLI flags Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> |
||
|
gavrielc
|
51788de3b9 |
Skills engine v0.1 + multi-channel infrastructure (#307)
* refactor: multi-channel infrastructure with explicit channel/is_group tracking - Add channels[] array and findChannel() routing in index.ts, replacing hardcoded whatsapp.* calls with channel-agnostic callbacks - Add channel TEXT and is_group INTEGER columns to chats table with COALESCE upsert to protect existing values from null overwrites - is_group defaults to 0 (safe: unknown chats excluded from groups) - WhatsApp passes explicit channel='whatsapp' and isGroup to onChatMetadata - getAvailableGroups filters on is_group instead of JID pattern matching - findChannel logs warnings instead of silently dropping unroutable JIDs - Migration backfills channel/is_group from JID patterns for existing DBs Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat: skills engine v0.1 — deterministic skill packages with rerere resolution Three-way merge engine for applying skill packages on top of a core codebase. Skills declare which files they add/modify, and the engine uses git merge-file for conflict detection with git rerere for automatic resolution of previously-seen conflicts. Key components: - apply: three-way merge with backup/rollback safety net - replay: clean-slate replay for uninstall and rebase - update: core version updates with deletion detection - rebase: bake applied skills into base (one-way) - manifest: validation with path traversal protection - resolution-cache: pre-computed rerere resolutions - structured: npm deps, env vars, docker-compose merging - CI: per-skill test matrix with conflict detection 151 unit tests covering merge, rerere, backup, replay, uninstall, update, rebase, structured ops, and edge cases. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat: add Discord and Telegram skill packages Skill packages for adding Discord and Telegram channels to NanoClaw. Each package includes: - Channel implementation (add/src/channels/) - Three-way merge targets for index.ts, config.ts, routing.test.ts - Intent docs explaining merge invariants - Standalone integration tests - manifest.yaml with dependency/conflict declarations Applied via: npx tsx scripts/apply-skill.ts .claude/skills/add-discord These are inert until applied — no runtime impact. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * remove unused docs (skills-system-status, implementation-guide) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> |