Are you still sending screenshots to the session to explain what's wrong with UI? It was a pain for me for quite a long time, now things changed.
Agent in session could interact with browser page and do checks automatically. Here is a short demo of it, works for claude and codex
@Samaytwt Yeah it's too many sessions, impossible to handle. But I don't get your point. If developer runs 5-8 sessions in parallel it means he saves your business time by developing feature faster. Probably it worth paying him even more?
@sl1ma4 The only way to really be able to use Fable is havin 200$ plan. Even 100$ is not enough, weekly limit is fine but not 5h. I was on 5x Max abd asked Fable to run a security review of the project, 5h limit went from 0 to 34% from one task
The thing I didn't expect from AI review: it's most useful in the language I'm worst at.
In TypeScript it tells me things I knew. In Python it tells me things I'd never have caught — because I don't have ten years of "that looks wrong" in Python.
Ran a code-health review on a repo. 30 test files.
Ran it again. Same commit, nothing touched. 50 test files.
Neither run was lying. One had counted tests/. The other had counted every tracked spec in the repo. The metric never said which population it meant, so each run quietly picked its own — and then confidently reported a number.
The bug wasn't in the counting. It was that "how many test files" isn't a question until you say which files count.
Fix: every metric now pins its own population as tightly as it pins its command. Whole tracked repo, filtered by name, same way every time.
A number moves when the code moves. That's the whole contract.
Check it out - https://t.co/S9Xe2eyLK2
@pcshipp I am using opus 5 for most tasks. Fable 5 I keep for global, big and difficult tasks. Something like full project review or refactoring most of it