Astra for Coding: Why Are We Doing This Again?
lumpa
14 points
2 comments
September 09, 2026
Related Discussions
Found 5 related stories in 71.7ms across 6,054 title embeddings via pgvector HNSW
- Path to Astra: critical capabilities and frontier safeguards jithinraj · 117 pts · September 01, 2026 · 61% similar
- How concerned should we be about Astra's recurrent architecture? yurivish · 118 pts · September 03, 2026 · 60% similar
- I think Astra is absolutely amazing but I'm back to 5.6 for software engineering tosh · 11 pts · September 08, 2026 · 56% similar
- GPT-6 Astra makes major gains in the Artificial Analysis Coding Agent Index wertyk · 21 pts · September 03, 2026 · 53% similar
- Open AI X post on Astra matthieu_bl · 12 pts · September 03, 2026 · 53% similar
Discussion Highlights (2 comments)
xyzsparetimexyz
Great article. Ive had situations where models start off being good at using the edit tool in pi but as the context gets longer (or perhaps once its encountered a bad patch error when using the tool) it switches to frequently using Python for edits and sometimes sed for reading. I've also had to set up a system wide extension that blocks any bash calls containing 'find / '. No, sorry, you don't get to spend 5 minutes searching my whole nvme drive just to find a file in the Lucan local directory tree
elicash
1. After reading this article, I'm going to hear this music https://youtu.be/KVdqwD_bcPs?si=qo_3_9yZWiW3zEQW&t=86 in my head the next time I'm waiting for a response from my LLM. 2. The author understandably takes issue with the 35 hours. But I do think it's wrong to confuse the time it takes with the number of lines it ultimately writes. To quote Blaise Pascal, "I would have written a shorter letter, but did not have the time."