limux-a2a

Limux A2A

Use Limux itself as the live registry. Do not rely on generated files or persistent rosters. Prefer the installed limux command; use ./target/.../limux-cli only when testing this repo build.

Fast Launch

When asked to launch a peer from inside Limux, split first using the already-exported LIMUX_* values. Do not run identify, list-workspaces, or read-screen before the first spawn unless an env value is missing.

created="$(limux --json new-pane \
  --pane "$LIMUX_PANE_ID" \
  --surface "$LIMUX_SURFACE_ID" \
  --direction right \
  --command 'claude "Task prompt here. Parent surface if you need it: '"$LIMUX_SURFACE_ID"'."')"

child_surface="$(printf '%s\n' "$created" | jq -r '.surface_ref // .surface_id' | sed 's/^surface://')"
child_pane="$(printf '%s\n' "$created" | jq -r '.pane_ref // .pane_id' | sed 's/^pane://')"

If the fast launch fails with failed to connect to socket, retry that exact new-pane command with approved/escalated socket access. If it fails with Unknown option --json, switch to the repo-built ./target/debug/limux-cli or ./target/release/limux-cli and retry the same command. Only after those retries should you inspect socket/listing state.

Identity

Each Limux terminal should have:

printf 'workspace=%s\npane=%s\nsurface=%s\ntab=%s\nsocket=%s\n' \
  "$LIMUX_WORKSPACE_ID" "$LIMUX_PANE_ID" "$LIMUX_SURFACE_ID" "$LIMUX_TAB_ID" "$LIMUX_SOCKET"

Fallbacks:

limux --json identify
limux --json list-workspaces
limux --json list-panels --workspace "$LIMUX_WORKSPACE_ID"

Target exact peers with --surface <surface-id>; it is found in any workspace, even after its tab moved. Do not add --workspace to a surface: it restricts the search to that workspace, and a moved tab's LIMUX_WORKSPACE_ID is stale.

Spawn Panes

Launch tools directly with new-pane --command; do not create an empty shell and later inject a long escaped codex "..." line. Long injected launch lines can wrap or corrupt the shell input.