docs: add tool and model fallback RFC#346
Open
mason5052 wants to merge 2 commits into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds an RFC/design proposal describing a conservative, policy-driven fallback layer for tool failures, missing CLI tools, and model/tool-call failures (per issue #341), without changing runtime behavior.
Changes:
- Introduces an RFC outlining goals/non-goals, failure bounds, and security considerations for fallbacks.
- Sketches an illustrative configuration shape (pseudocode) for future implementation.
- Proposes incremental milestones for implementing the feature safely.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
mason5052
force-pushed
the
codex/issue-341-fallback-rfc
branch
from
e7d52ae to
1a7012c
Compare
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
Adds a docs-only RFC for configurable fallback when tools, missing CLI commands, or model/tool-call generation fail.
Problem
Issue #341 asks for broader fallback behavior, including similar-tool fallback, optional safe tool installation, and model/provider fallback. PentAGI already has retries, tool-call fixing, reflector recovery, mentor monitoring, planner support, Installer Agent concepts, and tool-call limits. Jumping straight to runtime fallback would risk hidden automation, unsafe installation behavior, or silent provider switches.
Solution
Add
examples/proposals/tool_model_fallback.mdas a conservative design proposal. The RFC defines goals, non-goals, current recovery behavior, problem cases, v1 design principles, tool fallback, missing CLI handling, model fallback, operator approval, visibility, configuration sketch, failure bounds, security considerations, open questions, and incremental milestones.The proposal keeps fallback disabled or policy-limited by default, requires visible bounded decisions, requires explicit operator approval for installs by default, rejects untrusted install commands such as curl-pipe-shell, and calls out that this should not reintroduce hidden queue or lifecycle state risks.
Refs #341
User Impact
Users and maintainers get a focused design surface before any runtime fallback code lands. This should make future implementation safer to review and easier to split into small milestones.
Test Plan
git diff --checkgit diff --check upstream/main...HEADgit diff --name-status upstream/main...HEADexamples/proposals/tool_model_fallback.md