plandex-ai/plandex · error

error generating name for piped data: %v

Error message

error generating name for piped data: %v

What it means

In the LoadContext handler's goroutine, model.GenPipedDataName fails while auto-generating a display name for piped stdin content. The name-generation LLM call or its plumbing errored, so the context cannot get a name.

Source

Thrown at app/server/handlers/context_helper.go:172

						errCh <- fmt.Errorf("panic in GenPipedDataName: %v\n%s", r, debug.Stack())
						runtime.Goexit() // don't allow outer function to continue and double-send to channel
					}
				}()

				name, err := model.GenPipedDataName(model.GenPipedDataNameParams{
					Ctx:           r.Context(),
					Auth:          auth,
					Plan:          plan,
					Settings:      settings,
					AuthVars:      authVars,
					SessionId:     context.SessionId,
					Clients:       clients,
					PipedContent:  context.Body,
					OrgUserConfig: orgUserConfig,
				})

				if err != nil {
					errCh <- fmt.Errorf("error generating name for piped data: %v", err)
					return
				}

				context.Name = name
				errCh <- nil
			}(context)
		} else if context.ContextType == shared.ContextNoteType {
			num++

			go func(context *shared.LoadContextParams) {
				defer func() {
					if r := recover(); r != nil {
						log.Printf("panic in GenNoteName: %v\n%s", r, debug.Stack())
						errCh <- fmt.Errorf("panic in GenNoteName: %v\n%s", r, debug.Stack())
						runtime.Goexit() // don't allow outer function to continue and double-send to channel
					}
				}()

View on GitHub (pinned to e2d772072e)

Solutions

1. Inspect the wrapped %v cause for the model-side failure
2. Check model client configuration and backend availability/rate limits
3. Validate piped content size/type before invoking naming
4. Retry the request; naming is per-item and a transient model failure will not persist

Example fix

// before
if err != nil {
	errCh <- fmt.Errorf("error generating name for piped data: %v", err)
	return
}
// after
if err != nil {
	log.Printf("GenPipedDataName failed: %v", err)
	errCh <- fmt.Errorf("error generating name for piped data: %v", err)
	return
}

// bound and validate piped content before naming
if len(context.Body) == 0 {
	return errors.New("piped data body is empty")
}
if len(context.Body) > maxPipedSize {
	return errors.New("piped data body exceeds limit")
}

if err := <-errCh; err != nil {
	if strings.HasPrefix(err.Error(), "error generating name for piped data") {
		// fall back to a deterministic placeholder name
		context.Name = "piped-" + shortHash(context.Body)
	} else {
		return err
	}
}

When it happens

Trigger: The model's naming call (LLM/heuristic naming of piped content) errors — e.g. model client failure, context cancellation, or invalid piped content — inside the per-item goroutine.

Common situations: Model backend unavailable or rate-limited; request context cancelled while naming; oversized/unsupported piped content; missing model client configuration.

Related errors

• No model config found for: %s
• %v

AI-assisted analysis of plandex-ai/plandex@e2d772072e (2026-09-05). Data as JSON: /api/errors/7c2ed23b46a0b3a8. Report an issue: GitHub.