Repository navigation
feat: accessibility automation v1 (core + tauri + settings) - #47
Merged
Merged
Conversation
senamakel
marked this pull request as ready for review
March 28, 2026 00:25
AusAgentSmith
pushed a commit
to AusAgentSmith/openhuman
that referenced
this pull request
May 23, 2026
…nsai#47) * feat(accessibility): add core automation RPC + settings panel * added accessibility code
7 tasks
senamakel
referenced
this pull request
in senamakel/openhuman
Jul 10, 2026
…rged) #47/#48 merged; crate main (95fa263) now carries all three OpenAiModel host-parity features (auth styles #44, temperature suppression/override #47, merge_system_into_user #48). Re-pin the cutover branch from the local integration branch to released main so the vendor pin references published API. Core lib green. Claude-Session: https://claude.ai/code/session_018MnMVgnzxchtcs1DDUxTfF
senamakel
added a commit
to nocstah/openhuman
that referenced
this pull request
Sep 11, 2026
…nsai#47)\n\n* feat(accessibility): add core automation RPC + settings panel\n\n* added accessibility code\n
This was referenced Oct 4, 2026
12 tasks done
M3gA-Mind
added a commit
that referenced
this pull request
Oct 8, 2026
Takes the SDK's /memory/free-period route (sdk#49), the /memory/v1 dialect routes (sdk#45) and the Sarvam agent integration (sdk#46, #47). Additive only: no SDK type, method or route is removed or renamed, the crate stays 0.1.1 with the same dependencies, so neither lockfile changes.
12 tasks done
M3gA-Mind
added a commit
that referenced
this pull request
Oct 8, 2026
Takes tinychannels #50 (ChannelMessage.sender_name, the sender's display name; a WhatsApp LID-only sender stays <lid>@lid instead of +<lid>) and #47 (tokio-tungstenite 0.29 -> 0.30). - The gitlink and the compiled registry pin move together. The record points at the v0.1.11 release; each of its 11 platform digests is copied from the release's published checksum.toml, which matches GitHub's own asset digest. The release covers the same 11 platforms. - The gitlink now sits on the tag, so the source/module skew (13 commits past v0.1.10, tinychannels#49 among them) is gone and its exemption in module-pin-exemptions.json is removed. - sender_name: None at the 38 ChannelMessage literals that name every field; the 4 that spread from another message keep working. - Lockfiles: the three tinychannels crates 0.1.10 -> 0.1.11; tinychannels now depends on tokio-tungstenite 0.30.0, added beside the 0.29.0 that openhuman, axum and tinyliveagents keep, with tungstenite 0.30.0. Their dependencies already resolve in the lock (rand 0.10.2, sha1 0.11.0).
Closed
4 tasks done
senamakel
added a commit
that referenced
this pull request
Oct 23, 2026
Adds a review note to the remaining-security plan covering TinySecurity PR #47, which serializes secret-scope registration, approval-scope replacement, and retirement through a single module lifecycle lock so rejected changes preserve the live resolver. Notes the pushed owner branch, passing focused tests and Clippy, and that cross-platform CI and review are still pending. Auto-committed-on: cuttlefish Co-authored-by: Medulla <medulla@tinyhumans.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
rust-coreaccessibility automation subsystem (macOS-first) with ephemeral in-memory runtime state.openhuman.accessibility_*for status, permissions, session lifecycle, capture, input actions, and autocomplete flows.tauriCommands.ts.accessibilitySlicefor permissions/session/feature/error state and async lifecycle actions./settings/accessibilityand linked it in settings navigation/home.Problem
Solution
rust-core/src/openhuman/accessibility/mod.rsas a process-global engine with:AccessibilityAutomationConfigto core config schema/defaults and wired it intoConfig.rust-core/src/core_server.rsdispatch table with allopenhuman.accessibility_*methods and response typing.src-tauri/src/commands/openhuman.rs, command registration insrc-tauri/src/lib.rs, and typed bridge event emission (openhuman:accessibility) with host notifications on key events.Testing
yarn -s compilecargo check --manifest-path src-tauri/Cargo.tomlnpx prettier --check .npx eslint .npx tsc --noEmitcargo fmt --manifest-path src-tauri/Cargo.tomlnpx vitest run --config test/vitest.config.ts src/store/__tests__/accessibilitySlice.test.ts src/components/settings/panels/__tests__/AccessibilityPanel.test.tsxcargo test -p openhuman-core accessibility --manifest-path src-tauri/Cargo.tomlImpact
accessibility) with defaults; existing config loads remain backward compatible via serde defaults.Breaking Changes
Related
unknownfallback where feasible.