proomt

Search

Search posts, papers, and topics

All posts

LobstersNicolas Dehandschoewercker6 min readintermediate

I expected better from Google

Summary

The authors of the open‑source project mobile‑use discovered that Google’s Artemis repository contains large blocks of identical Python code, examples, and even the same agent name without any attribution. They document the exact file diffs, the removal of their names via a force‑push, and the omission of their benchmark results from a public leaderboard. The post argues that this violates Apache…

  • Google’s Artemis repo includes verbatim copies of mobile‑use code (adb tunnel, Hopper agent prompt, messaging example) and a bug that was later fixed.
  • The original commit history listed the mobile‑use authors, but a force‑push removed their names and replaced them with different authors.
  • Attribution required by the Apache‑2.0 license was not preserved, and the project’s leaderboard omitted the authors’ benchmark scores.
  • The authors have opened a public issue and contacted Google, requesting proper credit and an explanation.

Attribution is a legal and community‑trust requirement for open‑source licenses. When a large company republishes code without credit, it discourages contributors, creates extra maintenance overhead, and undermines the collaborative model that fuels innovation in AI‑driven mobile automation.

6/10

Related reading

  1. Changing the game: How Google uses agentic AI to secure hundreds of millions of lines of code

    Google’s AI & Infrastructure team built an agentic pipeline (Mantis) that runs pre‑submit AI‑driven scans on every code check‑in, validates findings with a fast triage agent (AST + call‑graph analysis) achieving >92% precision in <1 min, then auto‑generates fixes via a bug‑fix agent. Localized threat models and a two‑step scan cut false‑positives to ~3% and prevent hundreds of vulnerabilities eac…

    Google Cloud Bloggoogle.com4 min
  2. Towards Self-Driving Codebases

    The post argues that AI agents could eventually handle low‑level engineering tasks—bug fixing, debugging, UI consistency, growth experiments—if the dev toolchain is made “agent‑legible”. It outlines missing primitives (global memory, code‑base rot prevention, better dev environments) and proposes a bootstrapping process to measure and improve a repo’s “agent readiness”. The piece is largely specu…

    Hacker News front pagedetail.dev9 minHN12099
  3. How to upskill enterprise AI builders by using daily micro habits

    Google Cloud Consulting proposes a four‑pillar micro‑learning framework for enterprise AI upskilling: 5‑minute browser‑based exercises, pre‑configured sandboxes, daily streaks, and delivering runnable code each session. A pilot (Advent of Agents) showed >150k participants, 859k code runs, and a 31% daily return rate, suggesting short, frictionless tasks improve engagement versus traditional bootc…

    Google Cloud Bloggoogle.com3 min
  4. Why client SDK generation belongs in the open

    Google partnered with Speakeasy to open‑source their OpenAPI‑based multi‑language SDK generator, covering Python, TypeScript, Go, Java, C#, PHP, and Ruby. The move replaces a now‑defunct proprietary generator, reduces maintenance overhead to ~1 engineer, and adds a CLI and documentation server generator under AGPLv3.

    Google Developersgoogleblog.com3 min
  5. CloudBees vs Harness: Why Migration Isn't the Fix

    The article argues that Harness’s “free migration” offer hides significant downstream costs (training, pipeline rebuilds, compliance recertification) and that even after migration you still lack unified governance across heterogeneous CI/CD tools. CloudBees positions its Unify control plane as a tool‑agnostic layer that adds visibility, continuous governance, AI‑driven test selection, and hybrid…

    Codeshipcloudbees.com5 min
  6. CodeMidas: Scaling Agentic Coding RL Environments from Code Itself

    CodeMidas builds RL environments directly from open‑source code: agents explore a repo, infer a spec, generate tests from the original implementation, and filter tasks via execution checks. The pipeline yields 5,545 high‑quality coding tasks across 23 languages and 15 domains. Training the MiMo‑V2.5 agent with GRPO on this dataset improves benchmark scores by 8‑18% (e.g., DeepSWE +11.7%, ProgramB…

    Hugging Face Daily Papersarxiv.org1 minpaper