Conversation
The Android twin of the iOS port: from a bot's profile sheet, "Activity" lists what the bot did, newest first by day, each row with the app and action in words, the recorded arguments, and an outcome chip; "Team memory" lists the section's shared people, places, decisions and terms, answers proposals waiting for a tap (Remember / Skip), removes entries, and adds one by hand. Both are content surfaces; the sending policy, app scopes and fallback chain stay on the desktop, where the companion allowlist has always kept execution policy. Core gains the models, client calls and session loaders ported module-for-module from CompanionCore; the app gains two destinations through the navigator, root screen, chat screen and profile sheet, with the copy and the day grouping in rules objects so they can be tested without Compose. The decoding tests read the two fixtures the iOS branch captured. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
In plain language
The Android twin of the iOS PR: two screens, reached from a bot's profile sheet.
The sending policy, app scopes, and fallback chain from #903 are not ported, on purpose: a paired phone may change a bot's model and profile but no other bot settings, so execution policy stays on the desktop.
What changed
android/core:ActivityRow,ActivityPage,TeamMemoryEntry,TeamMemoryPage,TeamMemoryEdit; client calls mirroringCompanionCore; session loadersloadActivity,loadTeamMemory,editTeamMemory.android/app:BotActivityScreen,TeamMemoryScreen,ActivityRules,TeamMemoryRules; two new destinations (Activity,TeamMemory) through the navigator, root screen, chat screen and profile sheet.Test plan
./gradlew :core:test :app:testDebugUnitTest :app:assembleDebugStacked on the iOS PR (base
feat/trust-ios), which carries the companion allowlist and the fixtures.Platforms
🤖 Generated with Claude Code