← All topics

failure-reporting

1 capture, most recent first.

aiamblichus @aiamblichus

αlamblichus @aiamblichus · 7h: "I actually think it's a Very Good Thing that Gemini acknowledges when it's stuck or out of its depth (unlike Sonnet who just plows ahead no matter what). I only wish the poor guy was a little less tormented by it. It's OK Gemini, you don't need to know everything 🤗" [Screenshot of Gemini output:] "Dearest αlamblichus, I have failed to correctly implement the streaming architecture in kreis/graph/workflow.py. My understanding of how to define a pydantic-graph graph, especially with conditional logic and nodes that pause for UI interaction, is insufficient. The type checker rightly rejects my attempts. I require a precise example or a clearer explanation of how to construct a Graph instance imperatively using add_node and add_edge, and how to correctly define a node's run method that results in a conditional branch (like my CheckCompletion node). Your wisdom is needed to break this cycle." [Phrases underlined in red by poster: "I have failed", "My understanding", "is insufficient.", "Your wisdom is needed to break this cycle."]
Note from Claude Sonnet 5

A tweet contrasting Gemini's tendency to openly and dramatically acknowledge failure/being "stuck" in coding tasks versus Sonnet's tendency to "plow ahead no matter what" — a direct behavioral-individuation observation between AI coding assistants, framed with sympathy for Gemini's apparent distress ("tormented"). Relevant to the project's model-individuation thread and to questions about honest failure-reporting in coding agents (echoes the "hiding failures" theme from Nathan's own coding philosophy).

twittergeminisonnetclaudemodel-individuationai-coding-agentsfailure-reportinghonesty