plandex-ai/plandex · error

error generating name for note: %v

Error message

error generating name for note: %v

What it means

model.GenNoteName returns an error while auto-generating a name for a note-type context during LoadContext. The name-generation model call failed (API error, timeout, bad config), leaving the note context unnamed.

Source

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

				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
					}
				}()

				name, err := model.GenNoteName(r.Context(), auth, plan, settings, orgUserConfig, clients, authVars, context.Body, context.SessionId)

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

				context.Name = name
				errCh <- nil
			}(context)
		}
	}
	if num > 0 {
		for i := 0; i < num; i++ {
			err := <-errCh
			if err != nil {
				log.Printf("Error: %v\n", err)
				http.Error(w, err.Error(), http.StatusInternalServerError)
				return nil, nil
			}
		}
	}

View on GitHub (pinned to e2d772072e)

Solutions

  1. Check the wrapped error for model API failures
  2. Retry the load; name generation is transient-dependent
  3. Verify org model settings allow the naming model role
Defensive patterns

Strategy: retry

When it happens

Trigger: Thrown at app/server/handlers/context_helper.go:194 when the library encounters an invalid state.

Common situations: See trigger scenarios.


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