Capabilities

Windsurf IDE, in one view.

Windsurf IDE is being designed around the work that surrounds an AI coding agent: its conversation, its branch, its changes, and the moment it needs your attention. This preview describes the intended product, informed by the Termany foundation.

Keep the whole session in view

Arrange projects, tabs, and split panes around the way you work. The design brings running sessions together so you can follow an implementation, watch a test, and inspect a result without rebuilding your context in another window.

Give a Bot a repeatable role

Define a specialist by its instructions, preferred model, and working folder. The planned Bot workflow gives recurring tasks a recognizable owner, from implementation to review, while separate topics keep conversations focused.

Coordinate work, deliberately

The vision for group conversations is simple: a lead coordinates, specialists contribute, and mentions direct a request. Give each agent a clear responsibility and review the combined result before accepting changes.

Put review beside the work

Keep a file view, a code diff, and a local preview near the terminal that produced them. The intended workflow makes it easier to check a change against the task instead of treating a finished conversation as proof that the code is correct.

Know where each task lives

Branches and worktrees give parallel tasks their own working directories. The design keeps that context visible alongside session history, with remote connections and port discovery as part of the same workspace vision.

Make usage understandable

The planned usage view shows token activity and estimated model cost by project and model. Termany currently reads Claude and Codex transcripts for this purpose; broader agent support is not being promised here. Estimates do not replace a provider invoice.

Product preview

Your agents. A shared place to work.

Windsurf AI is a workspace concept for developers who already use coding agents. Agent access, credentials, model selection, and provider charges remain separate considerations. Final compatibility and release requirements will be published with the app.

See workflows for parallel development