Paseo Hub v0.10.0

0.10.0 - 2026-09-29

Added

• Scheduled triggers that run on a calendar recurrence, with time zones.
• Conversation continuity: a new arrival in the same issue, pull request, or thread continues the agent already working there instead of starting another, with explicit keys and an opt-out.
• A new arrival for a running agent steers it, including agents that run with scoped execution credentials.
• A Home page for new organizations with a setup checklist, a notice when provider events arrive with no trigger listening, and a seven-day overview.
• Saving a trigger validates its agent against the target daemon, so a model, mode, or provider the daemon cannot run is refused at save instead of failing the first run.
• A startup_timeout setting for machines that need longer than the default two minutes to start an agent.

Changed

• Upgrade Paseo daemons before upgrading Hub: conversation continuity needs the current daemon.
• One consistent interface across sign-in, organization administration, projects, connections, triggers, and instance settings.
• The trigger editor walks four numbered steps: what arrives, who may send it, where it lands, and what runs there.
• Trigger forms list only the events Hub handles, and label events require the label they match.
• Alerts say what happened, and empty pages no longer draw empty tables and panels.
• Paseo shows Hub executions under their trigger's name instead of an execution id.

Fixed

• Active agents keep their execution credentials across Hub restarts and reconnect to the same daemon agent.
• Long rendered prompts reach the agent in full.
• New GitHub agents receive their reply tool, and preserved legacy workflows dispatch again.
• The sidebar and breadcrumb stay on the page that is visible while the next one loads.
• Unsupported methods on the execution MCP route return 405 instead of an HTML page or a 500, and a daemon sending an invalid WebSocket close code no longer crashes Hub.

Paseo Hub v0.9.0

0.9.0 - 2026-09-04

Added

• Linear connections and signed issue, assignment, and comment triggers, with scoped context and workflow replies.
• Optional invitation email delivery, account email verification, and password recovery for configured deployments.
• Cardless seven-day Hosted trials, live plan presentation, open signup, and initial organization creation.
• Daemon-backed model, execution mode, and thinking-option selection in trigger setup.
• Dashboard help links, trial countdowns, and guided daemon setup from empty states.

Changed

• Hosted configuration now centers on organization-level, single-agent triggers with an equivalent visual editor and YAML document. Existing project workflows migrate at startup, while advanced multi-step workflows remain runnable as YAML.
• Trigger setup requires explicit daemon, agent, model, execution mode, and thinking choices when those capabilities are available.
• Daemon enrollment separates presence from workflow execution through explicit permissions while remaining compatible with legacy scope-based daemons.
• Dashboard navigation, copy hierarchy, and loading states now preserve the current scope and page shape.

Fixed

• Self-hosted Hub login and browser mutations honor the configured public origin behind TLS-terminating proxies.
• Discord and Slack thread context retains the conversation's root message after pagination and truncation.
• Daemon event-processing failures no longer escape their observer boundary and terminate Hub.
• Project-to-organization trigger migration preserves provider routing and repairs previously omitted implicit routes.
• Existing managed PostgreSQL databases start without requiring access to the postgres maintenance database.
• Failed provider connections return to Connections with the relevant recovery guidance.

Paseo Hub v0.8.0

0.8.0 - 2026-08-25

Added

• Pull-request-created and pull-request-label-added workflows now receive GitHub webhook deliveries.
• GitHub issue and pull-request triggers now react on the item with eyes when accepted, then +1 on success or -1 on failure.

Fixed

• Workflows triggered by Discord, Slack, GitHub, or manual input can use capabilities owned by another provider without losing valid authority.
• Workflow preparation failures retain their actual safe reason instead of being reported as daemon_unreachable.
• Deleting a Discord trigger message no longer leaves Hub retrying an impossible terminal reaction.

Paseo Hub v0.7.0

0.7.0 - 2026-08-23

Added

• A post-app onboarding step that gives operators the exact paseo hub login command, watches for their daemon to connect, and lands them in the Default project.
• An authenticated setup-resources API for guided clients to discover usable GitHub repositories, Slack workspaces, and Discord servers.

Changed

• Textual triggers now preserve the complete message as ${{ paseo.prompt }} while exposing parsed typed inputs separately.
• Startup logs print the complete browser URL for the running Hub.

Fixed

• Legacy project Activity URLs redirect to the active organization's canonical Activity page.
• Trigger prompts no longer lose mentions, typed-input headers, surrounding whitespace, or text before a suffix mention.

Paseo Hub v0.6.0

0.6.0 - 2026-08-21

Added

• Explicit GitHub triggers for created issues, pull requests, issue comments, pull request comments, and labels added to issues or pull requests.
• Case-insensitive GitHub label filters for the label changed by an event and the labels currently present on an issue or pull request.

Changed

• GitHub App onboarding now includes pull request events. Existing GitHub trigger names remain compatible with their previous behavior.

Paseo Hub v0.5.1

0.5.1 - 2026-08-20

Fixed

• Production startup ignores .env files, so zero-configuration launches use embedded storage even when run from a directory containing unrelated database settings.

Paseo Hub v0.5.0

0.5.0 - 2026-08-20

Added

• A zero-configuration local start with an embedded PGlite database, generated durable authentication secret, and first-run operator account setup.
• Browser-guided GitHub, Slack, and Discord app onboarding.
• Slack Socket Mode for local bots that do not have a public URL.
• A published @getpaseo/hub package that runs with npx @getpaseo/hub.

Changed

• Embedded Hub data now lives under $XDG_DATA_HOME/paseo-hub, falling back to ~/.local/share/paseo-hub.
• Configuration deployment can create or restore its implicit target project.

Fixed

• Slack username allowlists resolve consistently during provider setup.

Paseo Hub v0.4.0

0.4.0 - 2026-08-12

Added

• Execution-scoped worktree branch templates with ${{ paseo.execution.id }} for unique branches that remain stable through retries and recovery.
• Structured server logs for connection callbacks, provider event intake and routing, and workflow failures without recording event payloads or credentials.
• A ready-to-adapt single-repository team bot example.

Changed

• Provider reactions now follow the workflow run instead of each step, preventing duplicate reactions in multi-step workflows.

Fixed

• Discord replies create or reuse one conversation thread, and explicitly requested context includes the directly referenced message.
• Terminal workflow notifications are not lost when recovery and completion overlap.

Paseo Hub v0.3.0

0.3.0 - 2026-08-10

Added

• Multi-file configuration bundles with named environments, named agents, reusable prompt partials, and independently routed workflows.
• Explicit ${{ paseo.context }} access for provider context without rewriting ${{ paseo.prompt }}.
• Step-scoped GitHub credentials with repository, permission, and duration controls.
• Safe routing reasons for known events that no workflow accepted.

Fixed

• Self-hosted sign-in works over explicitly configured remote HTTP origins.
• GitHub App identity lookup uses scoped authentication and avoids public API rate limits.
• Daemon enrollment names are derived consistently from hostnames.

Paseo Hub v0.2.0

0.2.0 - 2026-08-09

Added

• Browser-based project configuration editing, including prompt partials and GitHub-backed configuration.
• Durable Hub login support for the Paseo CLI.
• Provider-specific passthrough options with provider-owned validation.
• Scoped preapproval for the exact Hub MCP tools authorized by each workflow step.

Changed

• Project selection and configuration flows are clearer in the dashboard.

Fixed

• Prompt partials remain available when configuration authority changes.
• Long configuration files and GitHub source controls remain usable in the configuration editor.
• Hosted deployments wait for a green main build before deploying to Fly.