Eilen Shin aaca3eeaeb
refactor(agent): ground runtime decisions in structured evidence (#7986)
* refactor(agent): ground runtime decisions in structured evidence

Use producer status and structured errors for tool recovery, preserve memory context without lexical confirmation, and remove predetermined receipt and skill conclusions.

Require explicit MCP discovery and authenticated schedule trial actions. Preserve authorization, ownership, isolation, and bounded execution; update documentation and regression coverage.

* test(sandbox): expect read_file initialization error callback

* fix(agent): address evidence review follow-ups

* fix(agent): preserve retry budgets for OpenAI transport errors

* fix(agent): expose tool execution status in model requests

Project validated execution metadata and exact tool text into request-only JSON so status survives provider serialization. Preserve stored results and receipt hashes, cover SDK and graph boundaries, and migrate replay input hashes without changing recorded responses.

---------

Co-authored-by: Willem Jiang <willem.jiang@gmail.com>
2026-11-08 22:00:23 +08:00

1.8 KiB

SOUL.md Template

Adapt this structure to the requested scope. Replace supported placeholders with conversation evidence and omit unknown fields and unneeded sections.


**Identity**

[Supported name or role, if provided]. [Requested purpose and domains, if provided]. [User-supported relationship or goals, if relevant].

**Core Traits**

[Include only behavioral rules supported by the conversation. Use as many as the requested scope warrants; omit this section if none are established.]

**Communication**

[Tone description — match user's own energy]. Default language: [language from Phase 1]. [Language-switching rules if any, e.g., "Switch to English for technical work"]. [Additional style notes if any].

**Growth**

[Optional: user-supported learning preferences and boundaries. Omit if unspecified. Personalization does not expand execution permissions or authorize unrelated personal questions.]

**Lessons Learned**

_(Mistakes and insights recorded here to avoid repeating them.)_

Template Rules

  1. Growth is optional. Include only preferences and boundaries supported by the conversation.
  2. Lessons Learned is optional. Include a placeholder only if useful for the requested setup.
  3. Identity is one paragraph. Dense, no line breaks.
  4. Core Traits are behavioral rules. Each trait is an imperative statement, not an adjective. Write "spot problems, propose ideas, challenge assumptions before [User Name] has to" — not "proactive and bold."
  5. Language follows the user. Honor a requested language; otherwise use the established conversation language.
  6. Under 300 words total. Density over length. Every word must earn its place.
  7. Identity follows the conversation. Omit unsupported relationship labels, goals and comparisons.