docs: document completion and custom endpoint settings keys (+ missing_docs bookkeeping for v0.2026.08.26)

[warp-factories]

What this feature does

Settings files can toggle Warp's built-in completions and your shell's own completions independently, and store non-secret custom inference endpoint definitions under agents.custom_endpoints. Shipped in v0.2026.08.26.17.59.stable_01 (2026-08-27).

Summary

missing_docs drift-watch for stable v0.2026.08.26.17.59.stable_01. Three always-on settings were missing from the all-settings reference; they share all-settings.mdx, so this PR both documents them and carries the run's bookkeeping (no open bookkeeping PR existed). A later drift-watch re-run on 2026-08-30 found the release already processed, deferred the remaining dogfood flag LrcActivitySignal, and refreshed the surface snapshot on this same branch.

Changes

src/content/docs/terminal/settings/all-settings.mdx

• Document terminal.input.warp_completions_enabled and terminal.input.native_shell_completions_enabled under [terminal.input]
• Document agents.custom_endpoints under [agents] (UI-managed object; credentials stay in secure storage)

.agents/skills/missing_docs/references/

• Map two new unreleased /factory integration routes -> internal
• Append triage verdicts for the release's surface_changes, changelog_review, and coverage findings
• Record last_release_processed.json and regenerate surface_snapshot.json
• Retarget the KittyImages map entry to files-and-links.mdx (it pointed at full-screen-apps.mdx, which covers the Kitty keyboard protocol, not the image protocol)
• Append a second, exhaustive pass's verdicts for the same release (see below)
• 2026-08-30: append LrcActivitySignal Gate 0 deferral and regenerate snapshot again

Second pass (exhaustive re-run)

A follow-up run swept the categories the standard run does not reach, and appended its verdicts here rather than opening a competing bookkeeping PR. It found one real gap, shipped separately as #658:

• Surface-scoped slash command check — the audit's slash check is repo-wide, so a command counts as covered when any page mentions it. Re-running it scoped by SlashCommandSurfaces found four GA GUI commands (/continue-locally, /handoff, /remote-control, /set-tab-color) missing from the table on agents/capabilities/slash-commands.mdx that presents itself as the complete list. /set-tab-color was undocumented anywhere. The CLI side is clean: all 32 TUI-capable commands are covered under agents/cli/.
• --weak-coverage (81 findings) — no docs. All are curated map entries whose page lacks a phrase derived from the internal flag name; spot-verified against code and docs.
• 23 potentially_stale_docs, itemized — no docs. Re-verified line by line; the new ledger row supersedes the bulk row from the first pass.

Content design plan

Short form (reference-table additions on an existing page):

• Reader and job: Someone configuring terminal completions or a custom inference endpoint via the settings file or Settings UI, looking up the exact key, type, and default.
• Gap today: all-settings.mdx listed neighboring completion knobs and execution_profiles but omitted these three always-on keys the audit extracts from code.
• Change: Three reference rows. Leaves out a new completions conceptual section (covered by terminal/command-completions/) and leaves endpoint setup on agents/inference/custom-inference-endpoint.mdx.

Unverified claims

None — defaults, toml paths, and UI labels verified against app/src/settings/input.rs, app/src/settings/ai.rs, and app/src/settings_view/features_page.rs.

Deferred findings

• GET /factory/{uid}/integrations/issue-tracker/issues and POST /factory/{uid}/integrations/slack/connection-test-greeting — Gate 0; Factory REST API unreleased; mapped internal
• agents.warp_agent.other.usage_display_unit — Gate 0; dogfood behind PricingTransparency
• NativeShellCompletions flag other→dogfood — Gate 0; settings above are the documentable surface
• LrcActivitySignal flag added (dogfood) — Gate 0; tracked by snapshot only until promotion
• Changelog UI/bug-fix items (#15515, #15258, #15424, #15395, #15346, #13967, #15221, #15505) and already-documented knobs (#15365, #15340) — no docs
• Factories EA launch bullets — major launch, already documented
• 23 potentially_stale_docs — style_lint / known ai credits false positives

/cc @dannyneira

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 30, 2026 4:08pm

[warp-for-oss]

@warp-factories[bot]

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[warp-factories]

This PR was generated with Warp.

Comment @warp-agent on this PR to send it follow-up work.

 

[warp-for-oss]

Overview

This PR updates the all-settings reference with completion and custom inference endpoint settings, and records missing-docs drift-watch bookkeeping for the release. The custom endpoint row and internal bookkeeping look consistent, but the completion settings documentation appears to publish dogfood-gated behavior as generally available.

Concerns

• The completion settings rows should either be deferred until the native completions feature is GA or explicitly state the availability gate. The diff records NativeShellCompletions as dogfood, and the runtime forces Warp-only completions when that feature flag is off, ignoring both completion toggles for most ungated users.

Verdict

Found: 0 critical, 1 important, 0 suggestions

Request changes

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[warp-for-oss]

⚠️ [IMPORTANT] These rows document the completion toggles as generally effective, but this PR also records NativeShellCompletions as dogfood-gated and the runtime forces WarpOnly when that flag is off. Public settings docs should either defer these rows until the feature is GA or state the availability gate so stable users do not try settings that are ignored.