[senamakel]

TinyVoice module manifests now accept TinyAgents 3.x, and its vendored TinyAgents pin advances to the 3.0.0 release candidate.

Depends on tinyhumansai/tinyagents#547; keep this PR draft until that release-prep PR merges.

Validation:

• cargo +stable check --manifest-path crates/tinyvoice-module/Cargo.toml --all-targets
• cargo +stable clippy --manifest-path crates/tinyvoice-module/Cargo.toml --all-targets -- -D warnings
• cargo +stable test --manifest-path crates/tinyvoice-module/Cargo.toml --all-targets (185 passed)

Refs senamakel/tinyagents#68
Part of tinyhumansai/openhuman#8088

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: dc733f93-daba-4a39-addb-a4e4ca9f1d88

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-23T00:08:19.099513Z	5a761f6	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[tinysweeper]

Tiny Sweeper review

Reviewed head: 5a761f6273dd2de37dbd983312e2790d8c9ff1e6

Verdict: Ready for maintainer review · Priority: none
Coverage: Reviewed 1 of 3 files; not reviewed: crates/tinyvoice…, vendor/tinyagent….
Pull request purpose (title): build: support TinyA…

Diagnostics and supporting details

Full summary

Pull request purpose (title): build: support TinyAgents 3.x. Tiny Sweeper completed its review; deterministic results follow.

Unreviewed paths

• crates/tinyvoice-module/Cargo.lock
• vendor/tinyagents

Review snapshot

Change surface	Files	Review signal	Count
Production	0	Active findings	0
Tests	0	Noted findings	0
Documentation	0	Resolved findings	0
Configuration	1	Pending checks/questions	0

Completeness: Complete
Test assessment: No supported feature-to-test mapping was available; this does not mean tests are absent or passed.

What changed

The TinyVoice module manifest's tinyagents-live and tinyagents-harness requirements move from the 2.x line to >=3.0.0, <4, aligning the workspace with the vendored 3.0.0 TinyAgents crates used through the [patch.crates-io] table. The practical effect is dependency resolution only: builds now require a 3.x TinyAgents, and if the workspace cannot satisfy that bound the module build fails at resolution rather than presenting any runtime or security surface. No source code, sinks, permissions, or CI configuration change. The Cargo.lock update implied by a new requirement range is not part of the reviewed diff, and the description's claim that the vendored pin advances to the 3.0.0 release candidate is not reflected by any submodule bump in the diff.

Features

• Modified — tinyagents-live requirement widened to 3.x: Standalone and workspace resolution for the module now requires tinyagents-live >=3.0.0, <4, matching the vendored 3.0.0 crate reached via [patch.crates-io]; incompatible resolutions fail the build instead of silently selecting 2.x. (crates/tinyvoice-module/Cargo.toml, crates/tinyvoice-module/Cargo.toml native-hotkeys = [])
• Modified — tinyagents-harness requirement widened to 3.x: tinyagents-harness likewise moves to >=3.0.0, <4, keeping both TinyAgents dependencies on the same major line and consistent with the vendored crate; the bound follows the existing caret-style range convention on these lines. (crates/tinyvoice-module/Cargo.toml, crates/tinyvoice-module/Cargo.toml native-hotkeys = [])

Tests

No supported feature-to-test mapping was produced. Test execution is not inferred.

Findings

No active actionable findings.

Before merge

None.

Agent review details

critique

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: The answered critique lane finds no correctness defect in the manifest change and notes the new ranges match the vendored 3.0.0 crates plus the existing convention; it also notes Cargo.lock is not updated in this diff and must be kept in sync.
• Lane summary: The change widens the tinyagents-live and tinyagents-harness requirements from the 2.x line to >=3.0.0, <4, matching the vendored 3.0.0 crates in vendor/tinyagents and the pinned submodules used via [patch.crates-io]; keep Cargo.lock in sync, which this diff does not touch. No correctness defect in this manifest change. _The code index does not reflect this commit, so retrieved context may be out of date._

security

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: The answered security lane reports nothing to report: a version-range bump with no code change, no new sink, and no permission or CI change, and any unsatisfiable range surfaces as an immediate build failure.
• Lane summary: This is a dependency version-range bump for tinyagents-live and tinyagents-harness from 2.x to 3.0.0–<4; there is no code change, no new sink, and no permission or CI change. Its only real effect is resolution: if the workspace cannot satisfy >=3.0.0, the module build fails, which would surface immediately in CI rather than as a subtle security defect. No repository rule is violated — the ranges are caret-style bounds (`>=3.0.0, <4`), matching the existing convention on these lines. Nothing to report. _The code index does not reflect this commit, so retrieved context may be out of date._

tests

• Conclusion: Neutral
• Scope reviewed: all assigned evidence
• Lane summary: No behavioural change: nothing outside documentation, configuration and tests.

commits

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: The answered commits lane reports no sensitive content in committed files.
• Lane summary: No sensitive content in committed files. _The code index does not reflect this commit, so retrieved context may be out of date._

description

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Positive: The answered description lane confirms the manifest edits match the stated range change but notes the body claims a vendored TinyAgents pin move to the 3.0.0 release candidate that the diff does not make.
• Lane summary: The diff widens the two TinyAgents manifest requirements from `>=2.1.4, <3` to `>=3.0.0, <4`, which is exactly what the description says. One gap: the body claims the vendored TinyAgents pin advances to the 3.0.0 release candidate, but no gitlink/submodule bump appears in the diff, so the recorded pin is unchanged — the manifest edits are correct as written, but the description should not claim a pin move this PR does not make. _The code index does not reflect this commit, so retrieved context may be out of date._

Evidence and run details

• Models: ladder/vectors-oai3, deepseek-v4.1-flash
• Spend: $0.001045
• Tokens: 146114 input · 3434 output · 30216 cached · 28 embedding
• Updated: 2026-10-23T00:26:33Z

Head	State	Pass summary
5a761f6273dd	ready for maintainer review	0 active finding(s), 0 resolved finding(s) (at 2026-10-23T00:26:33Z)

[tinysweeper]

tinysweeper found nothing blocking. Approving.

Diagnostics

Total spend: $0.0010