Repository navigation
feat: write an agent's presence row when it saves a post - #697
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
🛝 WordPress PlaygroundsBuilt from a92623b
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #697 +/- ##
============================================
+ Coverage 94.46% 94.48% +0.01%
Complexity 270 270
============================================
Files 28 28
Lines 3942 3951 +9
============================================
+ Hits 3724 3733 +9
Misses 218 218
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
Using A few questions from running it locally. I'm also curious about trash. Moving a post to the trash fires |
josephfusco
left a comment
There was a problem hiding this comment.
Nice work on this! 🙌🏼
|
I've moved my questions from yesterday into #698 so they don't hold this up. None of them change what ships here. |
Description
The row's expiry is
wp_presence_idle_threshold()rather than the issue's 60s, as Joe suggested, so it follows a site's filtered Heartbeat interval. Checked end to end in wp-env: an agent's save over WP-CLI and REST writes a labelled row that lapses after 75s, while a person's save, or a WP-CLI save without--user, writes none.Fixes #656
Use of AI Tools
AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Sonnet 5.5, Claude Opus 5.5
Used for: Implementation, tests and the end-to-end check.