Roadmap

About 702 wordsAbout 2 min

The Spora roadmap is drawn from the public portion of spora-core/docs/backlog.md (the internal backlog has more items that aren’t ready for public disclosure). Items below are listed in priority order — the team is free to reorder as priorities shift.

For questions, suggestions, or to flag something as a higher priority, see Contribute.

High

No high-priority items currently — see below for medium and low priority items.

Medium

Parallel tool calls

Run multiple independent tool calls simultaneously within a single agent turn to reduce wall-clock wait. Note: the system currently handles parallel Tasks (multiple agents running concurrently), not parallel tool calls within a single LLM response.

Web Push notifications

Surface PENDING_APPROVAL alerts even when the browser tab is closed/inactive. Currently implemented via Mercure/SSE for real-time web notifications, but NOT browser Web Push API (Service Workers).

Agent-to-agent handovers

Handovers with various documents (conversation context, intermediate results, files, partial state) can happen in the future. The current parent_task_id chaining is the seed mechanism — it lets a follow-up task inherit the prior task’s task_history, so a second agent can pick up where the first left off — but it is not yet a first-class UX surface (no “send to agent X with N more steps” shortcut in the UI, no explicit per-document handoff format). Add: (1) a UI action to forward a COMPLETED task to a chosen agent with optional additional steps, (2) a typed handoff document schema (which sections of history, which intermediate results, which files), (3) per-agent routing rules for automated handoffs.

Notification optimizations

Bulk clear all notifications; e-mail alerts for scheduled run completions. Both are implemented: markAllAsRead() (/api/v1/notifications/read-all) and deleteAllForUser() (DELETE /api/v1/notifications) routes exist, and sendEmailForScheduledRun() runs after scheduled-run completion. Scheduled-run deduplication is already handled — Orchestrator::tick() suppresses notifyTaskCompleted() for tasks with a run_id (app/Agents/Orchestrator.php:238), so only notifyScheduledRunCompleted() fires.

Mobile UI improvements

Fix broken Agent sidebar on small screens; optimize Settings Menu for mobile viewports. Responsive sidebar implemented in AgentLayout.vue, AppsLayout.vue, and SettingsSidebar.vue.

Richer templating for scheduled-run prompts

Scheduled-run prompts support {{var}} and {{var:default}} substitution, but the engine is a single regex pass — preg_replace_callback('/\{\{(\w+)(?::([^}]*))?\}\}/', …) in ScheduledRunService::substituteVariables() (app/Services/ScheduledRunService.php:542) — not a real template language. There are no sections ({{#list}}), no inverted sections ({{^list}}), no iteration, and no filters; an unmatched placeholder is either left as-is or replaced by the run template’s default_value for that key.

A fixed set of built-ins resolves before the run’s own variables, so a template can reference current_date (alias date), current_time (alias time), current_datetime (alias datetime), day_of_week, day_of_month, month, year, agent_name, and user_name without declaring them (app/Services/ScheduledRunService.php:559).

To finish: (1) decide whether to adopt a full templating engine (or grow the hand-rolled substituter) and backfill the existing {{var}} syntax, (2) support lists and per-item rendering so one template can drive a multi-step run, and (3) publish the complete placeholder list in one place — it is currently split between the three private methods above and a partial mention in the API reference.

Low

The internal backlog has additional low-priority items (small UX improvements, performance tuning, edge-case bug fixes) that aren’t yet ready for public disclosure. They’ll be added here as they graduate to medium or high.

Versioning

Spora does not follow strict SemVer yet — pre-1.0 versions are tagged as 0.x.y and breaking changes can land in minor bumps. The plan is to lock to SemVer once the 1.0 release ships.

For the project’s tagging policy (tag from main only, after CI is green, never from a PR branch), see Contribute → CI and coverage.

How to influence the roadmap

  • File a feature request — open a GitHub Discussion in spora-ai/spora-core with the enhancement tag
  • File a bug — open a GitHub Issue with a clear reproduction
  • Contribute code — see Contribute for the PR workflow

What’s next