Skip to content
agentusehub

Deliver a software feature autonomously (partial)

Claude computer use produced 70 files for a planned feature but the code didn't work, so the author went back to manual work.

Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

Claude computer use produced 70 files for a planned feature but the code didn't work, so the author went back to manual work.

Reported experience

  1. What they did

    The user discussed the feature deliverables and agreed on a concrete plan with Claude, then granted it full autonomous control to implement the entire feature. Claude generated 70 files on its own without further input or tests. The user reviewed the output afterward.

  2. How it went

    The code did not work. The user deleted the branch, cleared the session, and returned to using Claude only for incremental pair-programming steps.

  3. Worth knowing

    The full autonomous run produced unusable output after the agreed plan, prompting immediate abandonment.

Example prompts

Try with Claude computer use
In my repo at [repo path], implement this feature: [feature description]. First write a short plan and the list of files you'll change, and wait for my okay. Then build it in small steps, running the tests after each step. Stop when the tests pass and I can run [command] to see it working, and don't delete files without asking.
Software & DevOps

Port a Chrome extension to Safari

The author had ChatGPT take the Session Buddy extension source from Chrome, port it to Safari and install it, taking about 20 minutes.

ChatGPT