docs(agents): persist durable state to cloud, not localStorage#3253
Draft
raquelmsmith wants to merge 1 commit into
Draft
docs(agents): persist durable state to cloud, not localStorage#3253raquelmsmith wants to merge 1 commit into
raquelmsmith wants to merge 1 commit into
Conversation
PostHog Code has no local database, so agents default to localStorage for state that should really live in PostHog cloud. Add a Persisting State section and a Forbidden Patterns entry directing account-scoped/durable state to @posthog/api-client from a core service. Generated-By: PostHog Code Task-Id: 9fe2069a-5b32-408f-98e9-f66969b41a30
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
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.
Problem
PostHog Code has no local database of its own, so agents building persistence default to
localStorageor host-local files. That's the wrong home for anything account-scoped: it doesn't survive a reinstall and doesn't follow the user to another machine. This is the same root cause behind the custom-instructions-clearing complaint raised in a Slack thread. The database exists, it's just remote (PostHog cloud, reached through@posthog/api-client), and agents don't reach for it by default.Changes
Adds a Persisting State section and a Forbidden Patterns entry to
AGENTS.md(CLAUDE.mdsymlinks to it). It's a decision rule, not a blanket ban:localStorageand host-local files stay correct for device-local ephemeral view state (panel sizes, last-open tab, dismissed hints). Anything account-scoped or durable (settings, custom instructions, preferences that should sync) persists to PostHog cloud via@posthog/api-clientfrom acoreservice.Refs #3251.
How did you test this?
Docs-only change. Nothing to run.
Automatic notifications