feat(web): add runtime Activity, replay, and decision controls - #548
feat(web): add runtime Activity, replay, and decision controls#548lidge-jun wants to merge 46 commits into
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks 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 |
…odex/native-activity-web # Conflicts: # structure/server_api.md
lidge-jun
changed the title
lidge-jun
changed the title
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 813d72d346
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| permissions: 'auto', | ||
| workingDir: JAW_HOME, | ||
| perCli: buildDefaultPerCli(), | ||
| presentation: { mode: 'activity' as const }, |
There was a problem hiding this comment.
This makes Activity the default presentation, but README.md still says the mode is a separate follow-on that is not enabled, while root AGENTS.md still describes both the Activity layout and approval UI as future layers. Users and maintainers will therefore follow documentation that directly contradicts the shipped default and controls; update README, AGENTS, CLAUDE, and the architecture guidance with this change.
AGENTS.md reference: AGENTS.md:L182-L183
Useful? React with 👍 / 👎.
| next(); | ||
| }); | ||
|
|
||
| app.get('/api/traces/activity-runs', requireAuth, (req, res) => { |
There was a problem hiding this comment.
The new Activity journal endpoints are absent from structure/server_api.md: its Traces row still lists only the three pre-existing routes, and its native-decisions section still says Activity controls are separate. Merely updating the aggregate handler count leaves the public API reference incomplete, so add both Activity read routes and their session/cursor contracts to the synchronized server API documentation.
AGENTS.md reference: structure/AGENTS.md:L10-L11
Useful? React with 👍 / 👎.
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. |
…tive-activity-web # Conflicts: # devlog # structure/str_func.md
…tive-activity-web
1 participant
Tool output and commentary appear in a bounded Activity disclosure while the existing message body retains the final answer. Display settings switch between Activity and legacy presentation, and live approval/question controls remain above the composer.
The stack base is
codex/native-activity-02atef1fb23bf125513fd9a595d46cded24c18107689. The isolated setup-error source and test oracle from PR550 are included.Validation: 537 explicitly selected behavioral tests passed at the final candidate, including 10 fresh-virtualization cases and 12 structured-hydration cases with preserved RED/GREEN evidence. Six obsolete source call-location checks were replaced with actual first-user/history/recycling behavior checks. Root/frontend types, server/frontend builds, asset validation, structure counts, and independent source/test/live reviews passed. Actual OS-fenced IAB runs verified Cursor setup error, two redirects in one native process/session, one exact final answer in canonical state/database/UI, actual UI Stop, owner-only reads, and history restoration. Each interval ended with owned processes reaped and unchanged protected-file fingerprints. The final documentation pin and test-only follow-up do not change the exercised production code.
Current follow-up UI evidence is IAB-only. Earlier Electron main/preload, responsive-layout, and Pi checks remain tied to the separately preserved
813d72d34baseline; they are not relabelled as fresh Electron verification. No merge, release, deployment, or messaging/TUI rollout is included.Exact-head CI at
184d9826b07e909d3b050626aa98eafcde908da5: Tests and Postinstall Platform Checks, with every job and both aggregates successful.