Repository navigation
fix(integrations): report effective Pi automation status - #1509
Merged
Merged
Conversation
Signed-off-by: phernandez <paul@basicmachines.co>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
23 tasks
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
1 participant
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.
Why
Pi reported an ambient default project and automation as on even when no project mapping or workspace trust allowed automatic recall/capture. This hid the remaining setup step.
What Changed
/bm-statusnow reports an explicit project orunconfigured, workspace trust, and effective recall/capture states: on, off by configuration, or blocked with a reason. It provides project setup and trust instructions as appropriate. Setup guidance and the README explain that a mapping alone does not enable automation.Implementation Details
The command formats the current validated configuration and the same exact
BASIC_MEMORY_PI_TRUST_WORKSPACE=1condition used by automation. Project ID precedence is preserved. No routing, trust enforcement, capture, or registration behavior changes.Testing
just package-check-pi: passed typechecking, all 15 tests, bundled reference consistency, and npm package dry run.just package-check: passed the consolidated agent package checks.git diff --check: passed.Risks / Follow-ups
This reports configuration eligibility, not a live Basic Memory connectivity probe. Existing configuration errors continue through the command's existing error path.
Closes #1503.