Commit Graph

468 Commits

Author SHA1 Message Date
Teknium 18bac64044 chore: map contributor email for icemeng 2026-08-15 00:32:35 -07:00
Teknium 5599dc048f chore: map hbasheer@student.42abudhabi.ae -> hxwvaa for contributor attribution 2026-08-14 22:33:44 -07:00
Teknium 0178aca4a4 chore: map Halldrix contributor email 2026-08-14 22:03:56 -07:00
Teknium 49e30440a2 chore: map contributor emails for mariobgsp (PR #83902 salvage) 2026-08-15 10:29:05 +05:30
Teknium e6daa7aba5 chore: contributor mapping 2026-08-14 21:57:41 -07:00
Teknium 25857671f7 chore: map contributor email for attribution audit 2026-08-14 21:56:33 -07:00
Teknium 0ea79484d2 chore: map contributor emails for cron salvage 2026-08-14 21:55:14 -07:00
Teknium 3bb83a9a51 chore: map contributor email for salvage 2026-08-15 10:22:47 +05:30
Teknium 169ff2db4f chore: add contributor email mapping for arccat-114 2026-08-14 21:44:28 -07:00
Teknium b2113202be chore: map contributor email for x1051445024 2026-08-14 21:36:41 -07:00
deacon-botdoctor ea4cfbb3d6 chore(contributors): map loulanyue email 2026-08-14 21:24:36 -07:00
Teknium 1d958880b3 chore: contributor mapping for Ufonik88 2026-08-14 21:20:03 -07:00
Nicolas Formenton 9184915c42 fix(desktop): skip stale journal duplicate folds
The inflight-turn journal can outlive the turn it recorded (reclaim,
reconnect or restart races skip the settle that clears it). On session
resume the fold then re-appends journaled assistant rows to a transcript
that already holds the committed replies, so the conversation ends with
duplicate answers in scrambled order. The fold also carried the stale
entry's streamId onto the resumed state on an idle resume, which kept the
journal entry alive (persistInFlightTurnState only clears when streamId is
null) and re-folded the same tail on every open.

Detect text-level staleness before the append path: when every recoverable
journaled assistant row already exists as committed text in the base
transcript, treat the entry as caught up and clear it. Only keep a stream
target when the resumed session is genuinely running (keepPending), so an
idle resume self-heals instead of re-folding.
2026-08-14 21:10:13 -07:00
Teknium cb3ca0af0e chore: add contributor email mapping for razultull 2026-08-14 20:40:24 -07:00
Hermes Agent 12d99312aa chore: map contributor email for nicolasdmolina 2026-08-14 20:40:15 -07:00
Teknium 8064550025 chore: map contributor email for attribution audit 2026-08-14 20:24:51 -07:00
Teknium 99033ab1f0 chore: map contributor email for PINKIIILQWQ 2026-08-14 20:24:42 -07:00
Teknium 2b3c505463 chore: map salvaged contributor emails (audit_pr_attribution) 2026-08-14 20:24:32 -07:00
Teknium 62dbd87b1b chore: map contributor email for salvaged PR attribution 2026-08-14 20:24:15 -07:00
Teknium b9482484f7 chore: map contributor email for attribution audit 2026-08-14 20:23:57 -07:00
Teknium 4faf12b9ce chore: map salvaged contributor emails (75day, KBANTH) 2026-08-14 20:23:47 -07:00
Teknium 5a23ab513c chore: map salvage contributor emails to GitHub usernames 2026-08-14 20:23:18 -07:00
Teknium 56121e528d chore: map contributor email (audit_pr_attribution) 2026-08-14 20:23:07 -07:00
Justin Bennington 832eb56b77 chore: map contributor email 2026-08-14 16:43:37 -07:00
Teknium 2eda1292f6 chore: map contributor email for #56522 salvage 2026-08-14 16:40:02 -07:00
Benjamin 47fd2eb7c8 fix(browser): strip PYTHONPATH/PYTHONHOME from browser-use CLI subprocess env
The browser-use CLI runs under its own Python (uv tool / uvx), which
can differ from Hermes's venv interpreter. PYTHONPATH/PYTHONHOME
inherited from the agent process point at Hermes's venv
site-packages, and a child interpreter honors them ahead of its own —
so the CLI imported compiled C-extensions (pydantic_core) built for
the wrong interpreter and crashed with ABI mismatch /
ModuleNotFoundError (issues 83427, 84841, 86006, 86104; hits the
desktop backend on py3.14 and any shell exporting PYTHONPATH).

Strip both vars in _base_subprocess_env() — the CLI manages its own
environment and never needs Hermes's import path.

Salvaged from PR 83471 by Benjamin (@n1majne3), the earliest of two
independent fixes (also PR 84022 by @jklance16, PYTHONPATH-only);
regression test covers both vars and preserves unrelated env.
2026-08-14 16:22:38 -07:00
Teknium 3f7140fbed chore: contributor email mapping for salvaged PR #66538 2026-08-14 15:10:42 -07:00
Teknium 7f7ca89255 fix(dashboard): weave resume follow-scroll into sanitizer write path + contributor mapping
Follow-up to the salvaged #59713 commits: main's ChatPage gained the
PTY resume sanitizer + hydration machinery after the PR was authored, so
the write-callback follow-scroll is applied to the sanitized write path
(term.write(rendered, followScroll)) rather than the raw ev.data writes
the original diff targeted. Also adds the contributor email mapping.
2026-08-14 15:00:05 -07:00
Teknium 5269c8f69b chore: contributor email mapping for salvaged PR #50873 2026-08-14 14:50:45 -07:00
Buff Pesos 56f1afc834 feat(dashboard-auth): extend RFC 8252 native sign-in to password providers (system-browser autofill) (#75808)
* feat(dashboard-auth): extend RFC 8252 native sign-in to password providers

The desktop app runs password sign-in for gated gateways in an embedded
Electron BrowserWindow, where OS password managers (macOS Passwords /
iCloud Keychain autofill) cannot reach the form — Chromium-in-Electron
has no bridge to them, so users retype credentials by hand even though
the /login form already carries the right autocomplete attributes.

The existing RFC 8252 native flow (system browser + loopback + PKCE)
solves exactly this for OAuth providers, but was explicitly disabled for
password providers on the grounds that they have "no IDP round trip to
broker". The brokering is still worth having: it moves the credential
form into the system browser, where password-manager autofill just works.

Gateway-only change; the desktop needs no changes (runNativeLogin is
already page-agnostic), and older desktop builds pick the capability up
automatically once the gateway advertises it:

* /auth/native/authorize now accepts a supports_password provider:
  register the pending broker authorization as usual, then 302 the
  system browser to the interactive /login form with the opaque
  broker_state in the gateway's PKCE cookie (the same server-controlled
  channel the OAuth branch uses) instead of an IDP redirect.
* /auth/password-login: when the server-set PKCE cookie carries a
  broker handle, a successful credential check completes the pending
  authorization exactly like the /auth/callback native branch — mint
  the one-time loopback code, return the loopback redirect (validated
  loopback-only at authorize time) as `next`, clear the PKCE cookie,
  and set NO session cookies. A lapsed broker is a clean 400 telling
  the user to restart sign-in; a failed credential attempt leaves the
  pending entry intact so the user can retype.
* /api/status now advertises "native_pkce" whenever any interactive
  session provider is registered (previously only for non-password
  providers), so the desktop selects the system-browser strategy for
  password-only gateways.

Security posture is unchanged from the existing flow: loopback-literal
redirect_uri enforcement, PKCE S256 binding, single-use short-TTL codes,
constant-time comparison, and the same rate limiter on password attempts.

Tests: full authorize → /login → password-login → loopback → token →
bearer round trip, wrong-password keeps the pending entry, lapsed broker
→ 400, no-broker browser login keeps minting cookies, and the /api/status
advertisement for password-only gateways.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* fix(dashboard-auth): bind native password completion to the authorize-time provider

Review follow-ups for #75808:

* /auth/password-login now enforces that body.provider matches the
  provider recorded in the server-set PKCE cookie by
  /auth/native/authorize before completing a pending native
  authorization. /login renders a form for every session provider, so
  without this a native flow started for provider A could be completed
  with provider B's credentials, binding B's session into A's pending
  entry. The mismatch is rejected BEFORE credential verification (no
  session minted, no oracle) and preserves both the pending entry and
  the cookie, so the user can still submit the correct provider's form.
  Covered by a two-password-provider E2E regression test.

* Update the two docs spots that still said password-only providers do
  not advertise native_pkce (website desktop-native-signin guide and the
  auth_flows type comment in web/src/lib/api.ts).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* chore: map contributor email for #75808 (buffpesos)

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Co-authored-by: Brooklyn Nicholson <brooklyn.bb.nicholson@gmail.com>
2026-08-14 21:39:01 +00:00
kshitij 8134aadc18 chore: add SeashoreShi to contributor email map
Needed for PR #83207 salvage (fix: gateway platforms list crash).
2026-08-15 02:44:23 +05:30
kshitij 24a9203008 chore: map contributor email devops@sycamore.group → sycamoregroupltd 2026-08-15 02:23:56 +05:30
Teknium 4fe5090964 chore: contributor email mappings for salvaged PRs 2026-08-14 13:51:26 -07:00
Brooklyn Nicholson 6f49bc7d52 chore: map contributor email for the salvaged Windows updater commit 2026-08-14 15:48:31 -05:00
Teknium cc9358e525 chore: map contributor emails for salvaged commits 2026-08-14 13:09:44 -07:00
Teknium c2bf1ac70a chore: contributor email mappings for salvaged PRs 2026-08-14 13:09:37 -07:00
Austin Pickett 29d0cc2602 fix(dashboard): treat Ctrl+C serve shutdown as a clean exit (supersedes #52970) (#85711)
* fix(dashboard): suppress Ctrl+C shutdown traceback

* fix(dashboard): extend clean Ctrl+C exit to the Windows serve branch

The Windows loop-factory branch (and its pre-0.36 asyncio.run fallback)
runs under the same uvicorn capture_signals() re-raise as the POSIX
path, so console Ctrl+C leaked the identical KeyboardInterrupt
traceback there. Guard both serve calls with the same clean-exit
contract, keeping the import-resolution try/except comment accurate
(genuine serve-time errors still propagate).

Also ports the reworded POSIX-test docstring (the serve path is no
longer 'byte-for-byte unchanged'), wraps the POSIX KI test in
pytest.fail so a regression reports red instead of aborting the pytest
session, and adds the windows_only sibling test.

Extends #52970 to the whole bug class.

* chore: map contributor email for @wangs1203

* test(dashboard): actually exercise the pre-0.36 Windows fallback KI contract

Copilot review caught that patching uvicorn._compat.asyncio_run with
raising=False makes the import succeed, so _runner is non-None and the
extra asyncio.run patch never covered the fallback. Split it out: a
dedicated windows_only test halts the _compat import (None in
sys.modules) so the fallback branch is genuinely selected, then asserts
the same clean-KI contract on bare asyncio.run.

---------

Co-authored-by: Emiya·Leon <wangs.coder@gmail.com>
2026-08-14 12:02:05 -04:00
kshitij 1f8fdc7bd8 chore: map contributor email for @infocentr 2026-08-14 16:53:40 +05:30
Teknium 1e18f68148 chore: map contributor email for @dpersek 2026-08-14 01:31:26 -07:00
Teknium b9e7bead13 fix(gateway): coalesce same-tick async-delegation completions into one turn (#70300)
The async-delegation watcher drained the completion queue as a batch but
then delivered each event as its own synthetic turn, flooding the session
when a fan-out of background subagents finished together. Builds on the
per-process completion batching salvaged from PR #71898 (thanks
@yuzilongleif-collab) which coalesces concurrent _run_process_watcher
completions behind a short per-route fan-in window.

This commit adds the async-delegation half: group the drained batch by
full routing key (session_key + parent_session_id + platform/chat/thread/
user) and inject ONE consolidated turn per group. Durable-ack handling
stays honest: sibling rows are claimed up front via claim_event_delivery;
rows another consumer owns are excluded from the consolidated text (no
double-delivery); sibling claims are acknowledged only after adapter
acceptance and released (still pending) on failure. Events for different
sessions never coalesce, and a single-event group rides the existing
per-event path unchanged (latency and text identical).

Tests: 3 same-tick events -> exactly one adapter.handle_message carrying
all 3 results with all 3 durable rows delivered; 2 sessions -> 2 turns;
single-event path unchanged; failed batch releases claims and retries;
foreign-claimed sibling excluded and left pending.
2026-08-14 01:08:25 -07:00
Teknium 1292a31851 chore: map salvage contributor emails 2026-08-14 01:08:13 -07:00
kshitij 285eaaddc0 chore: add contributor email mapping for seze@andrew.cmu.edu
Maps to GitHub user Shedrackeze002 (PR #85616).
2026-08-14 13:15:56 +05:30
Teknium e8debfbdc3 chore: map contributor email for attribution audit 2026-08-13 23:43:54 -07:00
teknium1 5970ac73ab chore(skills/box): Hermes-compliance polish + docs registration
- author field to 'Chris Kim (iskysun96), Hermes Agent' convention
- 'Use this skill for' -> 'When to Use' section heading
- related_skills: google-workspace
- register auto-gen docs page, catalog row, sidebar entry
- contributors/emails mapping for iskysun96
2026-08-13 22:09:44 -07:00
Teknium d4b0039940 chore: map contributor email for @silence-de 2026-08-13 22:09:37 -07:00
Teknium bfff32ae8c chore: map contributor email for @sjungwon03 (PR #79787 salvage) 2026-08-13 12:31:02 -07:00
Teknium 4ef7ee9971 chore(contributors): map xaviersudre email for PR #75040 salvage 2026-08-13 11:56:43 -07:00
Teknium 991e2efdf4 chore: map contributor emails for cherry-picked commits 2026-08-13 11:49:24 -07:00
Teknium e70b187d51 chore: map salvage contributor emails 2026-08-13 11:49:14 -07:00
Teknium 3fc320c7c1 chore: map contributor email for cherry-picked commit (#72056) 2026-08-13 11:20:27 -07:00