roboomp
721f6d4a08
Codex review flagged that advertising `launchUrl` (http://localhost:<omp-port>/launch) as the visible `Copy URL:` breaks SSH/WSL/headless users: their local browser resolves the URL against the local machine (no OMP listening) and fails before ever hitting the provider. On terminals without OSC 8 support, they lose the manual `/login <redirect>` path entirely. Every OAuth-facing surface now shows the full authorization URL as the primary copy target and offers `launchUrl` as an additional "Local shortcut (this machine only)" line for wide-terminal local users who want the truncation-safe convenience: - MCPAuthorizationLinkPrompt renders `Copy URL:` with the full URL and appends the local-shortcut row only when `launchUrl` differs. OSC 52 clipboard staging in the MCP onAuth handler switches to the full URL (OSC 52 is a wire-level protocol — the terminal writes to the caller's LOCAL clipboard even when OMP is on a remote SSH box). - LoginDialogComponent.showAuth, selector-controller onAuth, setup-wizard sign-in, and the auth-broker CLI mirror the pattern: full URL first, launchUrl as an optional local shortcut. - Setup wizard uses `wrapTextWithAnsi`, not truncation, so the RFC 7636 §4.3 downgrade bug that motivated launchUrl is unreachable through it; still surfaces launchUrl for wide-terminal convenience. Regression tests in `packages/coding-agent/test/modes/controllers/mcp-authorization-link.test.ts` now assert: - Full URL is the primary `Copy URL:` line so SSH sessions can complete. - launchUrl still appears beneath as `Local shortcut (this machine only): …` when it differs from the full URL. - No shortcut row when launchUrl is absent OR equals the full URL.
@oh-my-pi/pi-coding-agent
Core implementation package for the omp coding agent in the oh-my-pi monorepo.
For installation, setup, provider configuration, model roles, slash commands, and full CLI reference, see:
Package-specific references:
Memory backends
The agent supports three mutually-exclusive memory backends, selected via the memory.backend setting (Settings → Memory tab, or ~/.omp/config.yml):
off(default) — no memory subsystem runs.local— existing rollout-summarisation pipeline; writesmemory_summary.mdand consolidated artifacts under the agent dir.hindsight— talks to a Hindsight server (Cloud or self-hosted Docker), retains transcripts every Nth user turn, recalls memories on the first turn of a session, and exposesretain,recall, andreflect.
Hindsight quickstart
- Run a Hindsight server (Cloud or
docker run -p 8888:8888 ghcr.io/vectorize-io/hindsight:latest). - Set
memory.backend = "hindsight"andhindsight.apiUrl = "http://localhost:8888"(or your Cloud URL). - Optional environment overrides (env wins over settings):
HINDSIGHT_API_URL,HINDSIGHT_API_TOKEN— connectionHINDSIGHT_BANK_ID,HINDSIGHT_DYNAMIC_BANK_ID,HINDSIGHT_AGENT_NAME— bank addressingHINDSIGHT_AUTO_RECALL,HINDSIGHT_AUTO_RETAIN,HINDSIGHT_RETAIN_MODE— lifecycleHINDSIGHT_RECALL_BUDGET,HINDSIGHT_RECALL_MAX_TOKENS— recall sizingHINDSIGHT_BANK_MISSION,HINDSIGHT_DEBUG
Switching backends mid-session is honoured on the next system-prompt rebuild and the next /memory slash command. Existing users with memories.enabled = true|false are migrated to memory.backend = "local"|"off" exactly once on first launch.