Node-based terminal manager for AI coding agents — tmux-backed terminals and parallel agent sessions as draggable nodes on an infinite pan/zoom canvas. macOS, Linux, and a browser Server Edition.
TypeScript adhdagent-orchestrationai-agentscanvasclaude-codecodexcoding-agentsdeveloper-toolselectrongeminilinuxmacosmultiplexeropencodeparallel-agentsterminalterminal-emulatorterminal-multiplexertmuxworkspace-manager
import { useEffect, useState } from 'react'
import { FIRST_SECTION_ID, type SettingsSectionId } from './nav'
import { parseProjectSectionId } from './project-settings-targets'
export interface SettingsTarget {
/** Section whose pane is shown when the search box is empty. */
active: SettingsSectionId
setActive: (id: SettingsSectionId) => void
/** Current search query. Empty = no filtering. */
query: string
setQuery: (q: string) => void
}
/**
* What the settings dialog is currently pointed at, and how a caller re-points it.
*
* Its own hook (rather than two `useState`s inline in SettingsPage) because the retarget rule is
* the load-bearing half of the deep-link feature and SettingsPage itself is untestable in
* isolation — rendering it mounts ~25 section modules, every one of which reaches for the preload
* API on mount.
*
* The rule:
* - A deep link (`initialSection` + a BUMPED `retargetNonce`) selects that section AND clears the
* query. Without the clear, a filter still sitting in the search box would hide the very pane
* the link just navigated to — the nav row would highlight over an empty page.
* - The nonce is what makes a REPEAT of the same section re-target: `initialSection` alone would
* not change, so the effect would not re-run.
* - Plain opens (the gear, ⌘, , the native menu) pass no section and never bump the nonce, so a
* query or a section the user chose inside the dialog survives.
* - A project section that no longer exists falls back to the first section — see `openProjectIds`.
*/
export function useSettingsTarget(
initialSection: SettingsSectionId | undefined,
retargetNonce: number | undefined,
/**
* Ids of the projects that currently HAVE a pane (SettingsPage's open-project list). `active`
* outlives the dialog — Canvas keeps it across opens — so a deep link to project X followed by
* closing X would otherwise leave the panel pointing at a section nobody renders: the nav row is
* gone and the main area is blank, with no way back but a click. Given the list, an `active` that
* names a project not in it falls back to the first section.
*
* Omitted (`undefined`) means "the caller has no list", not "no projects are open": the fallback
* is then skipped entirely, so a caller that has not loaded its projects yet cannot bulldoze a
* legitimate deep link. SettingsPage always passes the list.
*/
openProjectIds?: string[]
): SettingsTarget {
const [active, setActive] = useState<SettingsSectionId>(initialSection ?? FIRST_SECTION_ID)
const [query, setQuery] = useState('')
useEffect(() => {
if (!initialSection) return
setActive(initialSection)
setQuery('')
}, [initialSection, retargetNonce])
useEffect(() => {
if (!openProjectIds) return
const projectId = parseProjectSectionId(active)
if (projectId === null) return
if (openProjectIds.includes(projectId)) return
setActive(FIRST_SECTION_ID)
}, [active, openProjectIds])
return { active, setActive, query, setQuery }
}