Repository navigation
Conversation
Add apps/board with its README and build plan. check-engine-untouched.mjs fails when a branch changes any path outside apps/board, the agent-board workflow, and pnpm-lock.yaml since the merge base with upstream/main. The agent-board workflow runs it on every PR.
…checks to the plan S1 adds ZAIkai-style lint and dependency rules for the whole repo, failing only on added lines. K1 brings the omp rules, LSP, and a persistent env to every Claude Code session. B3 also probes Claude Code memory and preview tools in T3 threads, and B12 turns on Codex memories. B1 replaces the OS title bar with T3's dark one.
The desktop app is a Windows app with T3's dark title bar, launched from WSL with dev:windows. B2 joins a running WSL engine, boots one the way T3 desktop does, or installs T3 in WSL after asking. B4 updates the engine the way it was reached.
Electron main and preload, the agentboard://app protocol for production, and AGENT_BOARD_CDP_PORT remote debugging. A dark Tailwind shell with the empty sidebar and a pannable, zoomable dot-grid canvas, plus its viewport math and unit test. The agent-board workflow now installs with setup-vp and runs the board typecheck and unit tests.
Frameless-overlay title bar with T3's dark overlay colors and a dark top bar with a drag region at the overlay height. dev:windows and start:windows run the Windows build of Electron from WSL.
…nch adds - Port the ZAIkai anti-slop and generic project oxlint rules with per-rule tests. - Add dependency-cruiser boundaries with a baseline taken at the upstream merge base. - Add the added-lines check, Claude Code hooks, and a pre-push hook. - Fix the findings in the board shell and tighten its tsconfig. - Run the check, the node tests, and every PR base in the agent-board workflow.
…ode sessions - Add the agent-board local marketplace and the omp-kit plugin with PreToolUse, PostToolUse, Stop, SessionStart, and UserPromptSubmit hooks. - Read ~/.omp/agent/rules at hook time (OMP_KIT_RULES_DIR overrides), map omp scopes and interrupt modes, and fire each rule once per session. - Register typescript-language-server for the LSP tool and write the vp env into CLAUDE_ENV_FILE. - Add install-omp-kit.mjs with --config-dir for isolated Claude configs.
- Move the hook process entry to omp-kit/scripts/run-hook.mjs, the one place that reads process.env and stdin. - engine/hook.mjs and engine/rules.mjs take env and the rules folder as arguments.
chore(board): guard the engine boundary with a CI check
feat(board): scaffold the desktop app shell
chore(standards): enforce lint and dependency rules on added lines
feat(board): bring the omp rules, LSP, and persistent env to Claude Code sessions
The root merges each clean PR bottom-up and posts review-gated screenshots and video in chat at merge.
docs(board): record standing merge approval in the plan
- Find the engine through AGENT_BOARD_ENGINE_URL, a live server-runtime.json, a booted child engine, or one confirmed install. - Run every WSL command through wsl.exe with the login PATH, and directly on Linux. - Keep a safeStorage bearer, reissued once when the engine rejects it. - Build the connection runtime from client-runtime and list the engine's projects with an EngineStatus footer.
- Lane 1, 2, and 4 screenshots and a 46 s recording of boot, add, archive, and token reissue.
- Read each candidate's version before booting and apply the client's own orchestration protocol rule. - Offer the install of the current release when no compatible runtime remains. - Bundle the T3 packages into the main process so it can reach that rule.
The board reaches T3's own engine in WSL, the background service, and starts, installs, or updates it through t3 when needed. A board-owned engine would hold the T3 home's lock and keep T3 desktop from starting.
- The board finds T3's engine, starts T3's own service with `t3 service install`, or installs or updates T3 after one confirm. - It never runs an engine of its own and never stops the service. - It holds the distro awake while it runs and releases it on quit. - T3 commands run without VITE_DEV_SERVER_URL so the dev flag cannot move T3 to its dev state dir. - Saved tokens are scoped per WSL distro.
A missed perf rule no longer blocks a merge. O1 profiles and fixes every recorded miss at the end of the stack.
docs(board): record perf per PR and fix misses in a final O1 PR
feat(board): join T3's WSL engine and list its projects
… bar U1 follows B2. It restyles sidebar rows after Orca's, adds projects from a WSL folder, and shows Claude Code and Codex usage from the engine's provider usage limits in a bar along the window bottom.
…and cleanup W1 follows B3. It edits T3's worktree setup script, location, and branch naming, and drives T3's worktree cleanup. The plan now states that the board is a UI over T3's engine, styled after Orca in T3's dark tokens.
- Rebuild the sidebar rows as a shared set: SidebarRow, CountChip, PillRow, and ProjectHeader with its mark, menu, and collapse state that survives a reload. - Add projects from the Projects header: a folder dialog that starts in the WSL home, or a typed WSL path. The main process converts Windows paths with wslpath -u through the WSL runner, and a missing, Windows-drive, or duplicate folder shows its reason inline. - Draw a usage bar under the sidebar and canvas from the engine's providers[].usageLimits, so the board never calls a provider.
feat(board): style the sidebar like Orca's and add the usage bar
- Add scripts/engine-probe.ts, which starts an isolated T3 engine, mints its token through electron/engine.ts, and runs ten checks against a real Claude Code session. - Split the checks by theme and the engine connection and thread helpers into scripts/probe/. - Import wslEngine and the engine state with their .ts extensions so Node can load electron/engine.ts directly. - Typecheck scripts/ and run its tests with the app's tests.
- Add engine-findings.md, the ten check rows from a full probe run and the follow-up the failing check needs in B5 and B9.
feat(board): probe the engine behaviors the board depends on
…d cleanup - The sidebar's gear opens a settings screen with a category list, a back control, and an All projects or per-project selector. Fields show Inherited or Overridden and a project can reset an override. - Worktrees edits the setup script T3 runs in a new worktree, the worktree location, and branch naming through server.updateSettings. - Cleanup edits the automatic worktree cleanup rules, runs server.runStorageCleanup, lists the latest report, and removes one worktree with vcs.removeWorktree after a confirm.
- Add an optional docs list to the board file, appended when a send carries attachments. - The orchestrator card lists board.docs, so the list no longer depends on loaded thread history.
feat(board): add docs to a board as work and show worktree setup on agent cards
- Remove the peek drawer that floats over the canvas. - Draw its content in a Ticket tab after Chat, through a slot like Chat and Checks.
…ions - The second copy still said pstack-t3 installs at user scope, which B12 replaced with instance-only loading
feat(board): open tickets and agents in a Ticket tab, not a drawer
- An on-demand release job builds an installer and a portable zip with electron-builder and publishes board-v<version> - G1 first diagnoses why the fork has created no Actions runs since 2026-11-20 - G1 runs after P1, and O1 waits on G1
docs(board): plan G1, ship Windows releases of the board from GitHub
- A Claude summary on top of GitHub's generated list since the previous board-v tag, with GitHub's list alone as the fallback - The release job gains a prerelease checkbox; lane 2 checks the release body
docs(board): G1 writes release notes the way T3 does
- Previous-tag pick ignores upstream tags, and the notes file is summary plus GitHub's list
- Remove the Codex driver, tracker-write block, and developer_instructions path - List only Claude Code instances in the picker, usage bar, and Updates page - Drop the Codex tests and README sentences
docs(board): G1's unit box covers the release-notes script
- The last Codex fixtures become claudeAlt; the assertions are unchanged
chore(board): make Agent Board Claude Code only
- Adds workflow_dispatch to find out why the fork creates no runs.
- Pins electron-builder 26.16.1, the version apps/desktop uses. - Moves electron to devDependencies, which electron-builder requires.
- Gates, builds, packages, writes SHA256SUMS and notes, then runs gh release create. - release-notes.mjs puts a Claude summary over GitHub's generated list when a key is set. - A release job in agent-board.yml runs the same script on workflow_dispatch. - README says how to install and how to cut a release.
- release-notes.mjs puts a Claude summary over GitHub's generated list when a key is set. - A release job in agent-board.yml runs release.mjs on workflow_dispatch. - README says how to install and how to cut a release.
- The Linux build copies the uninstaller out of the installer stub without the CRC NSIS appends, so the uninstaller aborted with an integrity error. - CRCCheck off in a custom header fixes it, and SHA256SUMS covers the download. - Resource editing stays on, as in apps/desktop.
- g1-review-install.png shows the Start menu entry after a silent install. - g1-review-launch.png shows the installed app with the engine connected.
- Drops the zip from the targets, release.mjs, SHA256SUMS and the README. - CRCCheck off applies only to the uninstaller pass, so the installer keeps its integrity check. - One place for the win target, no restated signAndEditExecutable default, no unused release script. - README says a test pre-release needs a suffix such as -test.
feat(board): ship Windows releases of the board from GitHub
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
This PR changes the test suite by +367 test cases (browser 0, unit +367, server 0). Keep tests that would fail for a real reason, and test logic below the UI where it can be. See Testing. |
Member
|
Closing this: This cleanup belongs to your Agent Board fork. Against T3 Code, the pull request adds the entire separate application rather than removing a section from an existing sidebar. Please target the cleanup at your fork, where the Board sidebar already exists and the change can be reviewed on its own. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull request
Linear
Linear: T3-12
Summary
Removes the empty "Workspace" section from the board sidebar.
Nothing ever filled it, and it always said "Nothing here yet".
Visual explanation
flowchart LR subgraph Before A1[For you] --> A2[Browser] --> A3[Projects] --> A4[Workspace] --> A5[footer] end subgraph After B1[For you] --> B2[Browser] --> B3[Projects] --> B5[footer] endDetailed explanation
Sidebar.tsx: no longer renders the WorkspaceSection.Section.tsx: drops theemptyprop and its fallback text, which only Workspace used.docs/plan.md: the sidebar line now names only the Projects section.Screenshots
Not uploaded to GitHub. Local files:
Risks, migrations, and deploy notes
min-h-0 shrink, and theflex-1spacer above the footer is unchanged.dev:webin T3's browser. The scroll check used 30 injected rows, becausedev:webhas no engine.vp run typecheckpasses.🤖 Generated with Claude Code