Skip to content

Improvement

We doubled every task's sandbox to 4 vCPUs and 8 GB of RAM

By Sandeep Panda

Every Buildful task runs in a private sandbox that's deleted when the task ends. Since October 7, that sandbox has 4 vCPUs and 8 GB of RAM, up from 2 vCPUs and 4 GB, so installs, builds and test runs get twice the CPU and memory.

Each task still gets a sandbox of its own, so several tasks can run at once without sharing a machine. Read how the background coding agent works from task to pull request.

In the app

  • The sidebar has two columns: an icon rail for the app's pages, and your task list beside it, grouped by Today, Yesterday, Previous 7 days and Older. Press ⌘\ to hide or show the list.
  • If you cancel your plan, it stays active until the end of the period you paid for. You can resume it until then.
  • A long reasoning box has a See less button at the bottom, so you can fold it without scrolling back up.
  • Links in the agent's replies open in a new tab.
  • A long prompt no longer pushes the repo picker and send button off the screen. The task box scrolls instead.
  • Switching workspace with a task open takes you to that workspace's tasks.
  • Tasks
  • Workspace

About the author

Sandeep Panda

Co-founder, Bug0 · Building Buildful

Sandeep is building Bug0, which tests web apps with AI, and leads its core infrastructure and technology. He previously co-founded Hashnode and scaled it to millions of developers as its CTO. He wrote AngularJS: Novice to Ninja, co-wrote Jump Start HTML5, and thinks mostly about agentic testing and the infrastructure that makes AI-written code safe to ship.

Try it on your own repo

Describe a change. Buildful builds it, tests UI changes in a real browser, and opens a pull request. Your first 3 tasks are free, then 1,000 tasks for $10 a month. See pricing.

Start building