Replace the default workspace with a home screen

[gschier]

New installs no longer get an empty "Yaak" workspace. With no workspaces, the app shows a home screen to import from Postman, Insomnia, OpenAPI, or curl, open an example workspace, or start fresh. It also links to opening a folder or cloning a Git repository. Deleting the last workspace returns there.

The example workspace uses JSONPlaceholder and covers requests, variables, request chaining, and folder auth. It is created by a new cmd_create_example_workspace command instead of the importer, because the importer remaps request IDs without updating the response() tags that reference them. The web build declines that command for now.

Also removes an unused event sender from WriteDb.

[greptile-apps]

Confidence Score: 4/5

The PR is not yet safe to merge because fresh web users are presented with onboarding actions that predictably fail or do nothing on that host.

Findings

1.  Unsupported web onboarding actions ▶

Summary

This PR replaces automatic creation of the default workspace with an empty-state onboarding screen and adds a native command that creates a pre-populated example workspace.

• Fresh installations and deletion of the final workspace now lead to onboarding.
• Onboarding offers imports, an example workspace, a fresh workspace, folder opening, and Git cloning.
• The example workspace is created transactionally from an embedded JSON resource with regenerated model IDs.
• Database initialization no longer guarantees that a workspace exists.
• The web host explicitly declines example-workspace creation, but its onboarding UI currently exposes that and other unsupported actions.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Global models load] --> B{Any workspaces?}
  B -->|Yes| C[Restore latest workspace]
  B -->|No| D[Render onboarding]
  D --> E[Start fresh]
  D --> F[Create example workspace]
  D --> G[Import data]
  D --> H[Open folder or clone Git]
  E --> I[Create workspace model]
  F --> J[Native example-workspace command]
  J --> K[Regenerate placeholder IDs]
  K --> L[Batch upsert transaction]
  G --> M[Import plan and commit]
  I --> N[Navigate to workspace]
  L --> N
  M --> N

Loading

_{Reviews (1) · Last reviewed commit: "Restyle the home screen with launcher op..."}

[greptile-apps]

Unsupported web onboarding actions

On a fresh web install, this screen enables actions that the web host cannot run. “Try Yaak with a real API” calls the explicitly declined cmd_create_example_workspace command and shows an error instead of creating a workspace. The import choices also call declined commands, while opening a folder or cloning a repository is unavailable under the web host’s local-file, sync, and Git capabilities. Gate these options by host capability or provide supported web implementations so onboarding does not lead to errors or silent no-ops.

Knowledge Base Used:

• Client application architecture
• Desktop runtime and command bridge

[gschier]

We're going to implement those once the web version is live and promoted

[greptile-apps]

That makes sense. If the web build isn’t live or promoted yet, I agree this can be deferred as follow-up work rather than blocking this PR. Once it is enabled, the onboarding actions should be gated or implemented before users can reach this screen.