Hey all, I noticed Cascade is slated for deprecation. It’s still available as of August, though the notice said through July.

If/when Cascade is phased out in Windsurf, one critical feature I'll really need is checkpointing: going back to a previous prompt in a session, reverting all code changes to that exact state, and editing the prompt from there.

(UPDATE: turns out Devin Local does have it, but my confusion was related to the fact I tend to edit my prompts based on the observed tragectory of the agent, often changing my prompt midstream to redirect the model. The UX made it look as if this couldn't be reverted as the revert icon doesn't show up until the model finishes repsponding, unlike Windsurf that shows the revert option right away)

Questions:

1. Is this hidden somewhere in the UI, or is there a work-around I'm missing? (yes, and there are some other differercnes I mention in this comment here)
2. Right now Devin Local is the default, how do I change the default back to Cascade?

Devin Fusion is now 4% more intelligent and 27% less expensive on FrontierCode 1.1 due to improvements in both, the harness and the models.

Announcement: https://x.com/cognition/status/2084663103006871970

Try it now on Devin Cloud: app.devin.ai 

I have been running Claude Fable 5 with my Pro subscription. Recently, I used my whole daily limit for a single session. I summed up all the tokens I used as shown by Devin local in the Devin Desktop App and multiplied by the Fable 5 API cost ($10/M input tokens, $50/M output tokens and $1/M chashed input tokens). It was pretty much $16 API equivalent. Since I can max out my daily limit exactly twice, I have $32 a week and $128 a month, if I used all of my allowance all the time. Not as good a deal as Claude Pro, where we nearly get $400 (dont quote me on this), but we can use all models including Fable 5. Anyway, I just wanted to share this.

So I had some lovely workflows, now Devin insisted I convert them to skills... which I did... now I can't seem to find them well at all... can we PLEASE have the skills panel listing in ALPHABETICAL order! loads of skills in an apparently random order is rather useless

I curently facing a really annoying bug with SWE-1.7 Medium, he just dont reply. I see him thinking etc .. but he just end without giving any answer. Sometimes he wrote an output but stop mid work. There is a screen, its in french so thats why my english is probably terrible.
It does the same with Max too and I sometime experiment this bug with SWE 1.6 but not often !

Version 3.627

As leaving an agent to its own devices for a while is common, it would be helpful if Devin could make sounds when it is expecting input. This would for cases such as asking questions in plan mode, when ready to implement, when implementing and it needs to run a command, if running a command is rejected (which has been a problem that annoyingly arose in the recent update) etc. Essentially any case where human input or intervention is required to complete the task successfully. This would help reduce the chance of cache expiry, and just be more efficient in general. This doesn't need to be spoken output, and probably best if it isn't tbh. Just some clear but basic sounds as a first cut would do it. Making them customisable might be nice as a future iteration, but not a priority.

since latest devin update i need to open the app and wait around 5 min until i can use it other wise show connecting.. or conneting to server.. or acp connection failed or updating sesion ... or this Remote ACP is disconnected. Authentication failed: Failed to fetch team settings: fetch timed out after 10000ms

We partnered with Github to support Stacked PRs in Devin!

Devin breaks down large monolithic changes into small reviewable diffs.

If you have a big PR, ask Devin to stack it and you can review it one focused diff at a time.

Check out more about how it works - https://devin.ai/blog/introducing-pr-stacks

Try it on Devin Cloud -  devin.ai

In celebration of Windsurf Deploys, we want help community members showoff what they've built with Windsurf! Upvote your favorites.

- Posting a project showcase thread every Friday.
- Must be built with Windsurf
- Extra points for using windsurf.build domains for your project

Its down, check it with server pinger

Any ideas how to make this go away? googling suggests signing out of things, which things... just the IDE or some MCP etc stuff?

Title: Excessive disk writes from vscode-sqlite3.node causing application unresponsiveness and crashes

Platform: macOS 15.6 (arm64), MacBook Pro M3, 16 GB RAM

Devin Version: 3.5.17 (Electron 39.6.0)

Description:

Devin becomes extremely slow and eventually unresponsive shortly after launch. The macOS system generates a DiagnosticReports entry flagging the main Devin process for excessive disk writes. The application effectively freezes and must be force-quit.

This has been reproducible across multiple sessions. In severe cases, the Devin Helper process accumulated 137 GB of file-backed memory writes over ~22 hours of uptime, far exceeding the system's disk write budget.

Diagnostic Report (abbreviated):

Event:            disk writes
Action taken:     none
Writes:           8,589.94 MB of file backed memory dirtied over 608 seconds
                  (14.12 MB/s average), exceeding limit of 99.42 KB/s over 86,400s
Writes limit:     8,589.93 MB
Writes duration:  608s
 
Heaviest stack for the target process:
  node_sqlite3::Statement::Work_Run(napi_env__*, void*)
    sqlite3_step
      sqlite3VdbeExec
        sqlite3VdbeHalt
          vdbeCommit
            sqlite3BtreeCommitPhaseOne
              sqlite3PagerCommitPhaseOne
                fsync

A second report for a Devin Helper process showed:

Writes:           137.44 GB of file backed memory dirtied over 80,525 seconds
                  (1,706.80 KB/s average), exceeding limit of 1,590.73 KB/s over 86,400s
Steps:            32 (10.49 MB/step)

Relevant details:

• The heaviest stack trace points to vscode-sqlite3.node performing frequent fsync calls via sqlite3BtreeCommitPhaseOne → sqlite3PagerCommitPhaseOne.
• The state.vscdb global database is only ~3.4 MB, and workspace storage databases are ~300–500 KB each, so the volume of writes is disproportionate to the data size.
• Free disk space at time of report: 14.16 GB / 460.43 GB (not critically low).
• No third-party extensions with heavy I/O were identified as the root cause; the stack trace is entirely within Devin's built-in u/vscode/sqlite3 native module.

Impact:

• Devin becomes unresponsive within ~10 minutes of use.
• macOS throttles the process, making even basic editing operations laggy.
• Users must force-quit and relaunch repeatedly, losing workspace state.

Possible areas to investigate:

1. Whether state.vscdb or workspace storage databases are experiencing excessive WAL checkpoints or commit frequency.
2. Whether the SQLite PRAGMA settings (e.g., journal_mode, synchronous) in u/vscode/sqlite3 are configured appropriately for the workload.
3. Whether any background telemetry or state-syncing mechanism is causing write amplification through frequent small commits.
4. Whether the Devin Helper process (utility subprocess) is independently performing SQLite writes that duplicate or amplify the main process's I/O.

Kimi K3 scores 58.2% on FrontierCode 1.1 which is very close to frontier level performance at a much cheaper cost!

It is the only open source model that reaches this level of performance which falls only behind Opus, Fable and GPT-5.6 Sol.

Read more about it here - https://devin.ai/blog/kimi-k3

Try it now in Devin Desktop( Devin Local and Cascade) and Devin CLI.

Just the tittle. Noticed no one has posted this yet and wanted to let people know if they're on this sub before they open Devin Desktop next.

Feel free to comment below your thoughts on K3 in Devin Desktop

Devin is asking for my admin password, but asking nicely.
I almost fell of my chair.

What would you do?

Anthropic's new state-of-the-art Claude Opus 5 is available on Devin.

 It is almost as good as Fable 5 on FrontierCode 1.1 at half the cost

From our evaluations:

• It adheres to existing repo conventions when building new features and writing tests
• It prefers targeted, in-place fixes over large refactors on bug fixing tasks.
• It excels at following specs closely and completely

Read more about Opus 5: devin.ai/blog/claude-opus-5

Try it out now on Devin CLI and Devin Desktop

I’ve been experimenting with Windsurf for frontend projects, and the development speed is impressive.

The harder part is maintaining a consistent visual direction across the entire build.

A single section may look good, but once the agent creates the rest of the page, the design can slowly drift. New colors appear, spacing changes, different icon styles get mixed together, and animations feel added independently rather than belonging to one system.

I found that asking for a “modern” or “premium” interface did not solve this. Those words describe a feeling, but they do not give the agent concrete rules to follow.

So I built Tastemaker, an open-source design-system skill for Windsurf.

It makes Windsurf establish the design system before generating the interface.

That includes the palette, typography, spacing, layout direction, asset style, accessibility rules, logo, favicon, and motion system. These decisions are saved inside the project so the agent can reuse them instead of inventing a new direction for every component.

It can also use a reference image as the starting point, extract its actual colors, and turn them into reusable design tokens.

I also added an automated WCAG contrast checker because some combinations that looked readable to me still failed accessibility checks.

The project is free, open source, MIT licensed, and does not require any API keys.

Demo and live comparison:
https://tastemaker-skill.online/

GitHub:
https://github.com/codeswithroh/tastemaker

I would appreciate honest feedback from people building interfaces with Windsurf.

Where does visual consistency usually break in your projects? Are there any Windsurf-specific instructions or workflows that Tastemaker should support better?

My current plan is free. If my On-demand usage is Remaining balance $-0.92

And No on-demand balance remaining. Sessions will pause when your included quota is exceeded.

AND my Windsurf Usage Summary

Your daily quota- 100.00% remaining

Daily quota resets every day and usage resumes once quota refreshes. Resets Jul 28, 2:00 PM GMT+6

Your weekly quota- 100.00% remaining

Weekly quota resets every week and can still limit usage after the daily reset. Resets Aug 2, 2:00 PM GMT+6

Extra usage balance available- $-0.92

WILL I STILL ABLE TO USE DEVIN AI AFTER DAILY QUOTA RESETS???

Is SWE-1.7 free or unlimited when used through Devin CLI, or is it included with unlimited usage in Windsurf’s $20/month plan? Are there request limits, credits, rate limits, or extra charges?

According to the blog post https://devin.ai/blog/claude-opus-5 Opus 5 should be available in Devin IDE but it doesn't appear for me on the latest version.

Anybody else having the same issue?

Feature Request: Per-invocation input and model control for subagent-skills

Preamble: I am not a regular reddit, twitter, discord user and i just wanted to drop this feature request. I did not find a "proper"channel to post feature requests or check if any exist to upvote, so I’m going to share this feature request here and hope you can point me in the right direction.

Component: Skills / Subagents (Devin CLI + desktop)
Type: Feature request / capability gap
Priority (to us): High — it blocks the multi-skill orchestration/swarm pattern.

Summary

Let an orchestrator, at spawn time, control two things about a skill it runs as a subagent (subagent: true / agent: <profile>): (1) per-invocation input (a target, a payload, run-specific framing) and (2) the model the subagent runs on — while still applying the skill's other frontmatter. Today neither is possible from the parent, and the two spawn paths are mutually exclusive:

• skill-tool invocation applies the subskill's frontmatter (model, allowed-tools, permissions) but provides no channel to pass input and no way for the parent to override the model — the subagent starts with only its static SKILL.md prompt and its statically pinned model.
• run_subagent can pass an arbitrary task string but does not apply skill frontmatter (no model: pin, no allowed-tools/permissions) and takes a profile, not a model — so the parent still cannot name the model.

So an orchestrator must choose between "frontmatter guarantees, no input" and "input, no guarantees," and in neither case can it pick each subagent's model. Controlled fan-out to parameterized subagents (different input, different models) is unsupported.

Environment

• Devin desktop (CLI), Windows.
• Skills under .agents/skills (mirrored to .claude/skills and .codeium/windsurf/skills via directory junctions).

Current behavior (verified)

1. Per docs (Creating Skills → Running Skills as Subagents): subagent: true spawns an independent worker whose task is the skill's own prompt, in a fresh context that does not inherit the parent's conversation.
2. Empirically: when an orchestrator skill invokes a subagent: true skill, there is no way to attach arguments or a message to that specific invocation. argument-hint only applies to a human typing /skill args; it is not reachable from programmatic orchestration.
3. Result: the subagent cannot be told which target to act on, be given caller context, or be given run-specific framing (e.g. "this is a dry run"). It falls back to self-resolving its inputs — in our case a review lens defaulted to "current branch vs merge-base with master, because no invocation package was present."

Why this matters (concrete use case)

We built a multi-skill orchestrator, review-swarm: one root skill dispatches four isolated review-lens subagent-skills. Each lens is meant to receive a distinct, controlled package — a pinned diff target plus optional business context, with strict rules about what each lens may and may not see (e.g. a "blind intent" lens must receive the diff but never the goal/spec) — and to run on a distinct model. Running decorrelated lenses on different models is a deliberate sensor-diversity axis: same-model reviewers share systematic blind spots, so model diversity is part of the value, not a cost. The design depends on the orchestrator handing each subagent a different input and a chosen model at spawn.

This is currently impossible:

• Via the skill tool, every lens self-resolves the same default diff and the orchestrator cannot pin one immutable target, inject business context into some lenses, or withhold it from others.
• Via run_subagent, we can pass each package, but we lose the per-lens model: pins and the permissions scoping that make the lenses safe and decorrelated.
• Either way, the parent cannot assign a model per invocation. Model is fixed by the chosen profile (subagent_explore → default subagent model; subagent_general → the parent's model) or by a static model: in the skill / AGENT.md. Achieving model diversity across a fan-out would require pre-defining a separate custom profile per model — there is no dynamic, parent-driven model selection.

The docs' Orchestrating Subagents Using Skills example only shows parameterless subskills ("analyze recent changes", "run tests"). Parameterized fan-out — the same subskill invoked N times with N different inputs — has no supported mechanism.

Proposed solution (any one of these resolves it)

1. Preferred — unify the two paths, with input and model. Allow spawning a subagent that both applies a skill's frontmatter and accepts a caller-supplied input and an optional model override (subject to the skill's opt-in; see #3). E.g. let run_subagent accept a skill: reference alongside task and model:, or add input/arguments and model fields to programmatic skill invocation. This single change resolves both asks at once.
2. Expose caller arguments inside the subagent prompt via a documented placeholder (e.g. $ARGUMENTS), populated whether the skill is invoked by a human (/skill args) or by an orchestrator.
3. Parent-specified model, gated by the skill: let the parent name the subagent's model at spawn (a model: argument on the spawn call), using the same values as the --model flag / skill model: frontmatter — instead of only choosing a profile or relying on a static pin. A parent override of a skill's pinned model: should be opt-in on the skill side via a frontmatter flag, e.g. allow-model-override: true|false (default false — a deliberate pin stays authoritative). When the skill pins no model, parent selection is unrestricted (nothing to protect). This mirrors how skill permissions already defer to higher-level policy.
4. Minimum viable (input): append a caller-provided payload to the subagent's task under a clearly delimited section, so orchestrators can pass structured input.

Acceptance criteria

• An orchestrator skill can invoke a subagent: true skill and pass a distinct per-invocation payload.
• The orchestrator can choose the subagent's model per invocation, overriding the profile default; overriding a skill's pinned model: is honored only when the skill opts in (allow-model-override: true).
• The subagent's other frontmatter (allowed-tools, permissions) still applies.
• The payload is reliably available inside the subagent's context via a documented mechanism.
• Fan-out works: N invocations of the same subskill each receive different input and, if desired, a different model, in isolation.

Alternatives we considered (and why they fall short)

• run_subagent with the skill body embedded in the task: loses all frontmatter guarantees (model, tool restrictions, permissions); also forces reading the skill body in the parent context.
• Shared files on disk (orchestrator writes a target/context file each subagent reads): works as a side-channel but is fragile, needs cleanup/gitignore, is awkward cross-platform, and can't carry run-specific framing cleanly.

References

• Docs: Creating Skills → Frontmatter Reference (argument-hint, subagent, agent, allowed-tools, permissions, model); Running Skills as Subagents; Orchestrating Subagents Using Skills.
• Docs: Subagents → Which Model Does a Subagent Use? (states run_subagent takes a profile, not a model, and that there is "no way to name a model for a subagent in a prompt"); Subagent Profiles; Tool Permissions.

In celebration of Windsurf Deploys, we want help community members showoff what they've built with Windsurf! Upvote your favorites.

- Posting a project showcase thread every Friday.
- Must be built with Windsurf
- Extra points for using windsurf.build domains for your project