Senda — Roadmap

Where Senda is headed. This is intent, not a promise — priorities shift as the project and the people using it do. For exactly what changed and when, see the CHANGELOG.

Shipped in v0.1

The v0.1 line is feature-complete for everyday API work:

  • Core — 3-pane shell, multi-request tabs, all HTTP methods, collections as plain YAML folders.
  • Requests — params, headers, body (JSON, raw, form, multipart, GraphQL with schema introspection + autocomplete); auth (Bearer, Basic, API key, OAuth2).
  • Environments — `` interpolation with a precedence stack and gitignored *.secret.yaml overlays, editable in-app (collection or per-environment) with masked values + per-row reveal; optional at-rest encryption (AES-256-GCM, key in the OS keychain, SENDA_SECRET_KEY for headless decrypt).
  • Testing — per-request assertions, pre/post-request JS scripting (Goja sandbox), folder runner, load testing.
  • AI assist — optional LLM-suggested assertions from a response (bring your own key; Anthropic or any OpenAI-compatible endpoint).
  • Mock server — YAML-defined routes, scenarios, stateful CRUD resources, proxy passthrough, hot-reload.
  • Protocols — HTTP/HTTPS, WebSocket, and Server-Sent Events.
  • Chaining & flows — inline `` response references, plus declarative *.flow.yaml graphs (request / branch / setvar / loop / parallel / delay) runnable from the app or headless via senda run -flow.
  • OpenAPI spec editor — imported specs are kept in .senda/openapi/ and editable in-app via a structured form (operation summary/description + request-body fields), with edits written back in place so the rest of the document is preserved; each request links to its operation, pulling that operation’s request-body JSON Schema into the body editor for validation + key autocomplete.
  • And more — security scanning, JSON Schema response validation, import (curl / Postman / OpenAPI / HAR) and HAR response export, code generation, doc generation, rendered-markdown per-request docs, 13 themes, command palette, request history, file watch, cookie jar, read-only source-control diff (working tree vs HEAD) — plus a headless CLI and a terminal UI.

See the CHANGELOG for the full v0.1 detail.

Next

Near-term, roughly in priority order:

  • gRPC — first-class gRPC requests alongside HTTP and GraphQL.

Later / exploring

Bigger bets, not yet committed:

  • Visual flow editor — a node-graph canvas for editing *.flow.yaml (today flows are authored in the in-app raw-YAML editor with live validation, or by hand); React Flow is React-only, so this needs a Solid-compatible canvas or a hand-rolled one.
  • Split view — two requests side by side, for comparing environments or endpoints.
  • In-app change history — the read-only source-control diff (working tree vs HEAD) shipped in v0.1; next is surfacing git log --follow history for a request.

Non-goals

Things Senda deliberately won’t do, to stay small and local-first:

  • Cloud accounts, hosted sync, or telemetry.
  • A proprietary collection format — it’s plain YAML, and stays that way.
  • Electron — the native Wails shell is the whole point.

Have an idea? Open a feature request.