You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[scanner] ✨ Meetings agent-backend: codex and gemini safe profile or documented refusal #18552
Done in #18556 (merged 2026-11-17). codex and gemini are refused for meetings with a documented reason at config validation and in the Settings picker: codex has no flag that removes its shell tool (read-only commands could read the CLI sign-in and repeat it into a meeting), and gemini is not installed in the hive image and has no flag that turns off every tool. Per-backend latency is documented in src/docs/meetings.md.
@hivecommons-hive[bot] this issue was closed by @clubanderson as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.
Activity
clubanderson commentedon Nov 17, 2026
Done in #18556 (merged 2026-11-17). codex and gemini are refused for meetings with a documented reason at config validation and in the Settings picker: codex has no flag that removes its shell tool (read-only commands could read the CLI sign-in and repeat it into a meeting), and gemini is not installed in the hive image and has no flag that turns off every tool. Per-backend latency is documented in src/docs/meetings.md.
github-actions commentedon Nov 17, 2026
@hivecommons-hive[bot] this issue was closed by @clubanderson as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment
/reopenand it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.