Instruct agents not to wait (wait is for code generation)

Author: azzazzel

.agents/PINECONE-go.md

@@ -1026,13 +1026,15 @@ client, err := pinecone.NewClient(pinecone.NewClientParams{
 
 ### 5. **Not Waiting for Indexing** (eventual consistency)
 
+> **⚠️ IMPORTANT FOR AGENTS**: Include wait logic in generated code (e.g., `time.Sleep(10 * time.Second)`). **DO NOT** execute `sleep` commands in the terminal yourself.
+
 ```go
 // ❌ WRONG - search immediately after upsert
 ctx := context.Background()
 indexConn.WithNamespace(namespace).UpsertRecords(ctx, records)
 results, err := indexConn.WithNamespace(namespace).SearchRecords(ctx, &pinecone.SearchRecordsRequest{...}) // May return no results!
 
-// ✅ CORRECT - wait for indexing (10+ seconds)
+// ✅ CORRECT - wait for indexing (10+ seconds) - include in generated code
 ctx := context.Background()
 indexConn.WithNamespace(namespace).UpsertRecords(ctx, records)
 time.Sleep(10 * time.Second) // Wait for eventual consistency
@@ -1054,12 +1056,14 @@ if !ok {
 
 ## ⏳ Indexing Delays & Eventual Consistency
 
+> **⚠️ IMPORTANT FOR AGENTS**: The wait instructions below apply **ONLY to generated code**, not to the agent's own behavior. Include wait logic in the code you generate. **DO NOT** execute `sleep` commands in the terminal yourself.
+
 > **For complete information on eventual consistency**, see [PINECONE-troubleshooting.md](./PINECONE-troubleshooting.md#indexing-delays--eventual-consistency).
 
 **Key Points:**
 - Records become searchable 5-10 seconds after upsert
 - Stats update 10-20 seconds after upsert
-- Always wait 10+ seconds before searching after upserting
+- Always wait 10+ seconds before searching after upserting (include wait logic in generated code)
 
 **Production Pattern (Go):**
 
@@ -1113,10 +1117,10 @@ err = waitForRecords(indexConn, "example-namespace", len(records), 300)
 
 **Cause**: Eventual consistency - records not yet indexed
 
-**Solution**: Wait 10+ seconds after upsert before searching
+**Solution**: Wait 10+ seconds after upsert before searching (include wait logic in generated code)
 
 ```go
-// ✅ CORRECT
+// ✅ CORRECT - include wait in generated code
 ctx := context.Background()
 err := indexConn.WithNamespace(namespace).UpsertRecords(ctx, records)
 if err != nil {

.agents/PINECONE-java.md

@@ -1028,26 +1028,30 @@ Pinecone client = new Pinecone.Builder(apiKey).build();
 
 ### 6. **Not Waiting for Indexing** (eventual consistency)
 
+> **⚠️ IMPORTANT FOR AGENTS**: Include wait logic in generated code (e.g., `TimeUnit.SECONDS.sleep(10)`). **DO NOT** execute `sleep` commands in the terminal yourself.
+
 ```java
 // ❌ WRONG - search immediately after upsert
 index.upsertRecords(namespace, records);
 SearchRecordsResponse results = index.searchRecordsByText(...); // May return no results!
 
-// ✅ CORRECT - wait for indexing (10+ seconds)
+// ✅ CORRECT - wait for indexing (10+ seconds) - include in generated code
 index.upsertRecords(namespace, records);
 TimeUnit.SECONDS.sleep(10); // Wait for eventual consistency
 SearchRecordsResponse results = index.searchRecordsByText(...);
 ```
 
 ## ⏳ Indexing Delays & Eventual Consistency
 
+> **⚠️ IMPORTANT FOR AGENTS**: The wait instructions below apply **ONLY to generated code**, not to the agent's own behavior. Include wait logic in the code you generate. **DO NOT** execute `sleep` commands in the terminal yourself.
+
 > **For complete information on eventual consistency**, see [PINECONE-troubleshooting.md](./PINECONE-troubleshooting.md#indexing-delays--eventual-consistency).
 
 **Key Points:**
 
 - Records become searchable 5-10 seconds after upsert
 - Stats update 10-20 seconds after upsert
-- Always wait 10+ seconds before searching after upserting
+- Always wait 10+ seconds before searching after upserting (include wait logic in generated code)
 
 **Production Pattern (Java):**
 
@@ -1091,10 +1095,10 @@ waitForRecords("example-namespace", records.size(), 300);
 
 **Cause**: Eventual consistency - records not yet indexed
 
-**Solution**: Wait 10+ seconds after upsert before searching
+**Solution**: Wait 10+ seconds after upsert before searching (include wait logic in generated code)
 
 ```java
-// ✅ CORRECT
+// ✅ CORRECT - include wait in generated code
 index.upsertRecords(namespace, records);
 TimeUnit.SECONDS.sleep(10);
 SearchRecordsResponse results = index.searchRecordsByText(queryText, namespace, ...);

.agents/PINECONE-troubleshooting.md

@@ -17,7 +17,7 @@ This guide covers common troubleshooting issues that apply across all programmin
 
 **Solution**:
 
-1. Wait 10+ seconds minimum after upserting records
+1. Wait 10+ seconds minimum after upserting records (include wait logic in generated code, not in terminal commands)
 2. Check if records were actually upserted (no errors thrown)
 3. Use a polling pattern for production code (see language-specific guides for examples)
 
@@ -58,6 +58,7 @@ This guide covers common troubleshooting issues that apply across all programmin
 
 4. **Wait for indexing**:
    - Records become searchable 5-10 seconds after upsert
+   - Include wait logic in generated code (not terminal commands)
    - Use polling pattern in production code
    - See [Indexing Delays & Eventual Consistency](#indexing-delays--eventual-consistency) below
 
@@ -203,6 +204,8 @@ This guide covers common troubleshooting issues that apply across all programmin
 
 ## Indexing Delays & Eventual Consistency
 
+> **⚠️ IMPORTANT FOR AGENTS**: The wait instructions below apply **ONLY to generated code**, not to the agent's own behavior. When generating code that upserts records and then queries them, include wait logic in the generated code. **DO NOT** execute `sleep` commands in the terminal yourself.
+
 Pinecone uses **eventual consistency**. This means records don't immediately appear in searches or stats after upserting.
 
 ### Realistic Timing Expectations
@@ -222,6 +225,8 @@ After upserting records:
 2. **Stats wait**: 10-20 seconds for stats to update
 3. **Production pattern**: Use polling with `describeIndexStats()` to verify readiness
 
+**Note**: Include wait logic in generated code (e.g., `time.sleep(10)` in Python, `TimeUnit.SECONDS.sleep(10)` in Java). Do not execute sleep commands in the terminal.
+
 See language-specific guides for polling pattern code examples.
 
 ### Production Pattern: Polling for Readiness

.agents/PINECONE-typescript.md

@@ -967,12 +967,14 @@ console.log(results);
 
 ## ⏳ Indexing Delays & Eventual Consistency
 
+> **⚠️ IMPORTANT FOR AGENTS**: The wait instructions below apply **ONLY to generated code**, not to the agent's own behavior. Include wait logic in the code you generate (e.g., `await new Promise(r => setTimeout(r, 10000))`). **DO NOT** execute `sleep` commands in the terminal yourself.
+
 > **For complete information on eventual consistency**, see [PINECONE-troubleshooting.md](./PINECONE-troubleshooting.md#indexing-delays--eventual-consistency).
 
 **Key Points:**
 - Records become searchable 5-10 seconds after upsert
 - Stats update 10-20 seconds after upsert
-- Always wait 10+ seconds before searching after upserting
+- Always wait 10+ seconds before searching after upserting (include wait logic in generated code)
 
 **Production Pattern (TypeScript):**
 

.agents/PINECONE.md

@@ -239,7 +239,7 @@ Use for exact keyword matching with optional required terms and reranking.
 | Vector batch size   | 1000 records                               | Also 2MB total per batch          |
 | Query response size | 4MB                                        | Per query response                |
 | Metadata types      | strings, ints, floats, bools, string lists | No nested structures              |
-| Consistency         | Eventually consistent                      | Wait ~1-5s after upsert           |
+| Consistency         | Eventually consistent                      | Wait ~1-5s after upsert (include in generated code, not terminal commands) |
 
 ## Error Handling (Production)