Google Adds Cheminformatics Skills to Antigravity

In the repliesggbomb suggests making cheaper drafts with Wan or MiniMax before using Seedance for the final version. Simber asks about an older GTX 1070 laptop; lhjoyce first doubts its suitability, then qualifies the hardware advice with the lower-resolution option.

The speed report does not specify GPU, runtime, quantization or inference settings. The 8 GB remark concerns a different output resolution and does not establish the same 720p speed. These are users’ reports and workflow suggestions, not a reproduced benchmark.

Original dated October 28. Replies 4, 5, 6, 10, 11 and 14 were read November 3; the final hardware qualification is dated October 31. Promotional and reverse-proxy suggestions were omitted.

In the repliesThe author clarifies that AgenC used peak pricing for DeepSeek’s estimate; an off-peak calculation would be about $0.43. Alternative_Web7202 questions the lack of evaluation criteria and calls the post promotion for the harness. Other commenters dispute mechanical details in the animations.

One shared-harness comparison with unequal stopping conditions. The post links the tool; the author’s financial affiliation is unverified. Token totals include repeated and cached context across calls, not just generated output. No simulation or bill was independently reproduced.

Original posted October 24 at 18:16:37 UTC. The post and author pricing clarification were read October 26, alongside the reply questioning evaluation criteria. Cost figures remain estimates.

In the repliesThe author later posts that the allowance is gone. flyfre also complains about consumption, while Kayak suggests a lower-priced plan might be useful mainly for planning and review. These replies do not supply matched task logs or a billing calculation.

One account switching between models and workloads. The post does not establish a new universal quota formula or show that lower API prices increase subscription capacity. API billing and subscriptions are separate products.

Original dated October 23 at 21:04 in the served thread. Author replies 2 and 4 and human replies 3 and 5 were read October 26; the post includes screenshots but no complete usage log.

In the repliesQuanTradin emphasizes persistent state surviving the model switch. thelocalnode says recording rejected approaches helps avoid rebuilding failed ideas; the author agrees and links their own workflow write-up and templates. Neither reply independently reproduces the comparison.

The author promotes their own workflow. Exact Claude/Gemini versions, matched configurations and independently checked production logs are missing. Reported failures do not establish a general capability ranking or prove every model can safely share one working tree.

Original posted October 23 at 00:03:09 UTC. The author’s account and replies by QuanTradin and thelocalnode were read October 26. The workflow and comparison were not independently reproduced.

In the repliesIn reply 2, the author says comparison runs used the same prompt, fresh sessions and rolled-back source code. On October 22, reply 17 says they submitted a refund request and again saw overload errors during short translation requests. That is a refund request, not confirmation of payment back.

One user’s incident across different clients and routes. Reasoning settings and full task logs are missing; the post does not establish a provider-wide outage or prove that the model changed after its preview.

Original October 21 at 02:38 UTC; numbered author replies 2 and 17 read October 23. Other replies give mostly unmatched negative impressions, not a controlled reproduction.