Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The official 2.1.300 entry adds system prompts, tools and parameters to local session transcripts. Reviewing only visible chat messages is insufficient before sharing a file.
- A fuller transcript can help reconstruct a request, but does not guarantee the same response, tool result or execution environment.
- Local recording, uploading, retention and redaction are separate questions. This entry specifies no automatic upload, retention period or new recording-disable switch.
- The ineffective --sandbox and --no-sandbox flags on claude remote-control are removed and now cause an error. The changelog points to sandbox.enabled in settings.
The addition is request context, beyond chat messages
Claude Code's official 2.1.300 changelog says local session transcripts now also record each API request's system prompt, tools and parameters. The stated purpose is to let a transcript you choose to share reproduce a request exactly.
For troubleshooting, this provides request context beyond what the chat window shows. Reconstructing a request does not guarantee the same failure: the machine, external service state and subsequent tool execution can differ. Review the added request contents as well as the visible conversation before sharing.
Review each of the three added categories
Check the system prompt first, then the request's tool information, then its parameters. A conversation without sensitive chat text does not establish that the whole transcript is suitable for publication. Review the actual file you intend to provide.
If these fields contain internal instructions, nonpublic addresses, project material or credentials, handle them under your organization's rules before choosing recipients and a channel. Also identify which contents remain unmodified; this entry gives no automatic-redaction guarantee.
Check version, contents and recipients before sharing
First confirm which Claude Code version produced the transcript and whether it represents a local session or another execution mode. Do not extend this local-transcript change to every desktop, cloud or SDK record format.
Second, use your client's current official documentation to locate the transcript you intend to provide. Inspect its system prompt, tools and parameters, and confirm that it belongs to the affected session. Reviewing a chat screenshot alone is not enough reason to attach an unopened full transcript.
Third, prepare a sharing copy in a location permitted by your organization. Remove unrelated or restricted content, then check recipients and access permissions. Redaction can change a request, so explain what was replaced rather than presenting the edited material as an original request.
For a hypothetical example, a colleague only needs to determine whether a request included the expected tool information. Start with a relevant redacted excerpt rather than posting the entire project session in a public issue. Supply more context within authorized bounds if needed. This example was not executed.
Local storage does not establish upload or retention behavior
This entry describes a change to local transcript contents. It does not say the added fields are automatically uploaded by default, or specify new redaction guarantees, retention periods or recording-disable options. Check current product documentation and organizational configuration for data destinations and storage rules; the word local does not establish every aspect of data handling.
Move away from the removed Remote Control sandbox flags
The same version removes --sandbox and --no-sandbox from claude remote-control. The changelog says both flags previously had no effect; passing either now exits with an error. It directs users to sandbox.enabled in settings to sandbox sessions. If a launch script contains either old argument, review and remove that obsolete argument, then consult current configuration documentation for the required setting.
This migration note does not define all sandbox.enabled behavior across operating systems, settings layers or tools. Sandboxing constrains tool access, while transcript recording concerns saved request information. Changing sandbox settings is not an established way to disable recording, redact a transcript or prevent sharing.
Sources
Frequently Asked Questions
Will upgrading automatically add these fields to old transcripts?
The entry does not describe backfilling historical records. Inspect the actual transcript you plan to share. A current application version does not prove an older file has been supplemented.
Does tools in a transcript prove every tool ran successfully?
No. The change records tool information from API requests; it does not define a complete audit of every tool call and result. Providing a tool in a request and successfully executing that tool are different facts.
Does stopping Remote Control also delete or stop local recording?
The update establishes no such connection. Treat the Remote Control connection, transcript storage and sandbox configuration separately. Stopping remote access or removing obsolete flags is not a documented deletion or recording-disable action here.