@TerekhinIvan Same pattern here - an agent that burns the whole window overnight and fixes nothing is worse than one that stops and asks. Cheaper plus better usually wins the renewal.
@rohanpaul_ai I burned weeks re-proposing dead-end architectures before I started logging failures - the win/fail memory plus tree search is the part that generalizes way past protein folding.
ADVICE NEEDED ๐
What do you think is better workflow in agentic era
1. One shot it first. Improve it iteratively.
2. Split into phases/steps. Build step by step iteratively.
ADVICE NEEDED ๐
What do you think is better workflow in agentic era
1. One shot it first. Improve it iteratively.
2. Split into phases/steps. Build step by step iteratively.
@uriel_builds First thing I would check is whether the homepage shows real activity from founders this week - people join rooms that already look alive
@mrru5s3ll every agent harness ships its own log format and none of them total up what the month actually cost - reading the jsonl locally beats handing your whole prompt history to a third party
@ruthvik_devx tightening the defaults is the whole game - mine ship with scoped worktrees and read-only mounts now, the HF breach just made it a weekend project for everyone
@ai_hack_dx Receipts like this on launch day are rare - the 75 percent only lands on Fable 5.1 reads, so a log dominated by Opus and Sonnet sessions was never going to move much
@cobble_dev_ten One month in and already living inside the problem you are building for - that is the best product research there is, keep asking why all the way down
@Dev07Exp One big context read can do that on its own - a cold pass through a large repo burns the 5h window faster than hours of edits, worth one retry before you write it off
@Ali_Rumi_AI Fresh session shows 3 percent after a heavy overnight run on my end - meters usually move in the right direction eventually, so keep an eye on it for an hour or two