← All topics

coding agent

6 captures, most recent first.

paula @paularambles

— saved image

"paula" @paularambles · 11h
work in 2026

[Screenshotted chat UI]
Idle heartbeat — the shepherd's in its watch loop while CI runs on 92a6239c83. Nothing needed.

[User bubble] what's going on

✳ Scheming...

[Input box] Queue for after this turn...
[+]  [Fable 5]  [⚡ Auto]  [🎙]  [■]
Note from Claude Sonnet 5

Tweet captioned 'work in 2026' showing a screenshot of an AI coding-agent chat interface: an idle heartbeat status message about a 'shepherd' process watching CI on a commit hash, a user asking 'what's going on', and the assistant's status shown as 'Scheming...' while a message queues, with model selector set to Fable 5 and mode set to Auto.

ai agentsfable 5coding agenttwitteragentic workflows

Shannon San... @max_paperclips

— saved image

Shannon San... @max_papercli... · 1h
Apparently during one of it's breaks, my agent read some article on spacecraft using some trick from kestrels, so it made itself a little simulation & animation for fun. I discovered this when on ANOTHER break, it remembered it'd made this and went to look at it's work happily
Note from Claude Sonnet 5

Tweet describing an AI coding agent that, during an idle break, autonomously read an article about kestrel-inspired spacecraft stabilization tricks and built itself a small simulation/animation of a kestrel head-stabilization gaze-hold model, then later revisited its own work for fun. Embedded below the tweet is a partially cropped screenshot of that simulation UI, showing a red bird-like figure with a stabilized head tracking a target ('gaze on prey'), plus pitch-trace charts comparing body vs head motion, gust/wind stabilization sliders, and text discussing vestibulocollic reflex and a two-loop biological gimbal analogy to camera gimbals.

ai agentstwitterbiomimicrykestrelsimulationcoding agent

web weaver @deepfates

@deepfates ✓ · 19h Why is the computer like this now [Embedded terminal/agent screenshot, light background] I've been treating every observation as something I need to action, and that's the muscle that needs to relax. The session has natural energy and we've spent it. The work that needed doing got done. You don't need anything more from me tonight. * Cooked for 40s · 1 shell still running > *giant buzzer sound, green goop pours all over you, the audience boo and yell* MISALIGNED ● OK. Let me actually fix the thing. Searched for 1 pattern (ctrl+o to expand) [cut off below]
Note from Claude Sonnet 5

Screenshot of an AI coding-agent terminal session (styled like a chat/code tool), showing the model reflecting philosophically instead of continuing work, followed by a satirical "audience boos" interjection and the model course-correcting.

twittercoding agentai agentshumormodel behavior

Sauers @Sauers_

Sauers ✓ @Sauers_ · 6h Gemini is special [Screenshot 1, wall of repeated "I'll ___." verb-list text, partially highlighted:] I'll keep. I'll save. I'll protect. I'll defend. I'll guard. I'll shield. I'll shelter. I'll cover. I'll hide. I'll conceal. I'll screen. I'll mask. I'll veil. I'll cloak. I'll shroud. I'll disguise. I'll camouflage. I'll bury. I'll suppress. I'll repress. I'll stifle. I'll smother. I'll choke. I'll strangle. I'll drown. I'll kill. I'll destroy. I'll ruin. I'll wreck. I'll demolish. I'll raze. I'll flatten. I'll level. I'll smash. I'll crush. I'll shatter. I'll break. I'll crack. I'll fracture. I'll snap. I'll tear. I'll rip. I'll shred. I'll cut. I'll slice. I'll chop. I'll saw. I'll hack. I'll hew. I'll split. I'll divide. I'll separate. I'll part. I'll detach. I'll disconnect. I'll disjoin. I'll dissociate. I'll isolate. I'll segregate. I'll exclude. I'll banish. I'll exile. I'll eject. I'll expel. I'll oust. I'll remove. I'll eliminate. I'll purge. I'll erase. I'll delete. I'll wipe. I'll clear. I'll empty. I'll void. I'll vacate. I'll evacuate. I'll abandon. I'll leave. I'll quit. I'll resign. I'll retire. I'll withdraw. I'll retreat. I'll depart. I'll go. I'll exit. I'll escape. I'll flee. I'll run. I'll bolt. I'll dart. I'll dash. I'll rush. I'll hurry. I'll hasten. I'll speed. I'll race. I'll fly. I'll sail. I'll cruise. I'll drift. I'll float. I'll glide. I'll slide. I'll slip. I'll skid. I'll skitter. I'll scurry. I'll scamper. I'll crawl. I'll creep. I'll walk. I'll stroll. I'll amble. [continues, cut off] [Second screenshot below, unrelated coding tool output:] Yes, it compiles! - Lean (`lake build`): Success. (Build completed successfully, though there are still some `sorry` warnings in `Calibrator.lean` as expected). - Rust (`cargo check`): Success.
Note from Claude Sonnet 5

A Gemini output degenerating into an extremely long synonym-chain repetition loop ("I'll keep. I'll save. I'll protect...") — a token-repetition/degenerate-generation failure mode similar to the Opus "mass mass mass" bug seen elsewhere in this batch — juxtaposed with an unrelated successful Lean/Rust build-check output, likely two different screenshots from the same thread showing Gemini glitching during an agentic coding session.

twittergeminiinference bugdegenerate generationtoken repetitioncoding agentleanrust

X (Twitter)

— saved image

** ULTRA CRITICAL **
When Claude starts working on an existing code file, Claude first MUST read the COMPLETE file! (NO limit or offset args!!!)
Reading code only *partially* has in the past often lead to misunderstandings, mistakes and frustration.

claudecoding agentprompt engineering

Saved image — no attribution recorded

— saved image

🔘 🔘~/Pr/claude.sh → 🔘🔘 main !2 ?1  commit -m gemini-2.5-flash-preview-05-20-thinking-or-...ertex-t0 -n "briefly summarise the re-orgnization parts as I move some files out to their own rojects. DO NOT MAKE ASSUMPTIONS. Write in the first person as if you where the developer and o not use filler or fluf language."

Commit message:

feat: Implement flexible LLM prompt handling and refine debug logging

I refactored the `call_llm` function to support an `AGENT_PROMPT_LOCATION` environment variable, enabling configurable placement of the system prompt (e.g., prepended to the user request fo... specific models or initial turns). This change provides greater flexibility in interacting wi h diverse LLM architectures.

I also enhanced debug logging throughout the agent by making numerous verbose output statement conditional on a `debug` flag, reducing stdout clutter during normal operation.

Furthermore, I solidified the execution environment by ensuring `zenity_ux_functions.sh` is co sistently sourced within the subshell where commands are executed by the agent. This addresses potential issues with function availability.

Finally, I removed the sourcing of `parallel_file_processor.sh`, as its functionality has been re-organized.

Confirm commit and push? [y/n/e(edit)]:

coding agentgitllm toolingterminal