FreestyleChangelog — April 11, 2026
Git Search API, scheduled triggers, VM logs, and more.
After our launch on April 6th we got a ton of new interest and feedback from the community. This has been a week of targetted bug fixes, performance improvements and few new features. We focused on addressing concerns from users in our Discord and fixing onboarding pain.
This Friday we officially transitioned from the freestyle-sandboxes package to the freestyle package name. This will be our primary package going forward. bun i freestyle just works now.
The specific public changes that landed this week are as follows:
| Area | Change | Details |
|---|---|---|
| API | Git Search API | Search across repositories stored on Freestyle, available through the SDK. |
| API | Scheduled Triggers | Define cron-based schedules that automatically execute your code on a recurring basis. |
| SDK | skipCache parameter | Skip cache on snapshot and VM endpoints. |
| SDK | Snapshot delete | Delete snapshots programmatically via the SDK. |
| SDK | VM logger | Built-in logger support for VMs. |
| Dashboard | VM Logs | View logs from your VMs. Filter by service name. |
| Dashboard | Usage & Limits | VM usage tracking with per-account limits visible in the dashboard. |
| Platform | Landlock | Enabled Landlock in the VMs kernel for filesystem sandboxing. |
Coming Next
We're working rapidly on observability, documentation/sdk work and speed. We're upgrading our logging system a ton now and will soon have a unified logging experience across all services in the dashboard. We'll be exposing more tools in our CLI, SDK and API for understanding the state of your VMs, debugging failures and monitoring production workloads.
We want our SDK has the best support for complex usage patterns of agents using computers. To do this we're adding more integrations to support many common tools and services better in our VMs. We've revamped our integration architecture to automatically support docker-layer caching which should make all usage with it much faster.
Our median VM startup time right now is ~400ms and we hope to get that to <300ms by the end of this month.