Untrivial-ai/agent-orchestrator

Summary Markdown files do not remember the Rich preview display mode after switching away from a session and then returning to it. Steps to reproduce Open a worker session that has a Markdown file in its workspace, for example README.md. Open the file in the session file workspace / Files panel. Switch the file from normal file view to Rich preview. Navigate to a different session. Navigate back to the original session. Expected The Markdown file should still be in Rich preview mode. Actual The file returns to the normal file/code view. Why this happens The selected file display mode is kept as local React state inside frontend/src/renderer/components/FileContentPane.tsx: mode is initialized from initialMode. Clicking the toolbar buttons only calls setMode(...) locally. When the user switches sessions, the pane for the previous session unmounts/remounts. On remount, the effect resets mode back to initialMode. For center file tabs, initialMode comes from activeCenterFileRequest?.mod

Bug Reported by: @aditi (Aditi, core-BE) The session name / branch identifier displayed at the top of the agent session view is cropped on narrower windows, and the visual design makes it look like a clickable button when it is not. Repro Open a worker session in the desktop app (macOS) Observe the topbar area at the top of the session view — it shows the branch name (e.g. ao/agent-orchestrator-53/root) next to the status pill (e.g. "Idle") Cropping: When the window is narrow (or the sidebar is expanded), the branch name is truncated with ellipsis because the span uses truncate in a min-w-0 flex container that competes for space with the right-side actions (Kill, Orchestrator, bell, inspector toggle), which are all shrink-0. Button-like appearance: The branch text sits immediately next to the StatusPill, which has rounded corners (rounded-md), background fill, and an inset border — making it look like a pill/badge. The proximity of the GitBranch icon + monospace branch text to thi

Problem Terminal input does not support the platform-native macOS shortcuts for moving the cursor to a line boundary: Cmd+Left Arrow should move to the start of the current input line. Cmd+Right Arrow should move to the end of the current input line. This should feel like ordinary text editing elsewhere on the OS. The equivalent Windows behavior should also be preserved and covered explicitly: Home moves to the start of the line and End moves to the end. Ctrl+Left Arrow / Ctrl+Right Arrow must remain word-navigation shortcuts on Windows rather than being repurposed as line-boundary shortcuts. Source: User request in a local Codex session Reported by: Local user Analyzed against: 8d3517b1c3e2b3e48c7974282fb972202db6c757 (main, 2026-07-25) Confidence: High Priority: Low — this is a recurring input usability gap with existing keyboard alternatives. Reproduction Open an AO shell or agent terminal. Type a command or prompt long enough to place the cursor in the middle of the line. On m

Context (shared across all harnesses) AO stores a per-role model in agentConfig.model (backend/internal/domain/agentconfig.go:27). session_manager.effectiveAgentConfig merges the project base config with the role override and Spawn/Restore forward the resolved value into every adapter as cfg.Config.Model (backend/internal/ports/agent.go). Each adapter must opt in to forwarding that value to its CLI. Today only the Claude (claudecode/claudecode.go:172), Codex (#2869), and Kiro (config-file model key) adapters do. Every other adapter silently drops it, so a configured worker/orchestrator falls back to the CLI's global default model. Original report: #2769 Reference fix (the pattern to copy): #2869 (Codex) — adds an appendModelFlag helper called in both GetLaunchCommand and GetRestoreCommand, plus a GetConfigSpec model field and regression tests. Problem The opencode adapter (opencode, binary opencode) never forwards cfg.Config.Model to the opencode CLI. A opencode worker/orchestrator

Context (shared across all harnesses) AO stores a per-role model in agentConfig.model (backend/internal/domain/agentconfig.go:27). session_manager.effectiveAgentConfig merges the project base config with the role override and Spawn/Restore forward the resolved value into every adapter as cfg.Config.Model (backend/internal/ports/agent.go). Each adapter must opt in to forwarding that value to its CLI. Today only the Claude (claudecode/claudecode.go:172), Codex (#2869), and Kiro (config-file model key) adapters do. Every other adapter silently drops it, so a configured worker/orchestrator falls back to the CLI's global default model. Original report: #2769 Reference fix (the pattern to copy): #2869 (Codex) — adds an appendModelFlag helper called in both GetLaunchCommand and GetRestoreCommand, plus a GetConfigSpec model field and regression tests. Problem The Aider adapter (aider, binary aider) never forwards cfg.Config.Model to the aider CLI. A Aider worker/orchestrator configured wit