ClawWork v0.1 Wishlist: what should we ship first?

Hi everyone - welcome.

This issue is the main entry point for ClawWork v0.1 planning.

If there is anything you want ClawWork to support in v0.1, please share it here. Big feature, small paper cut, workflow improvement, setup pain, quality-of-life fix - all of it is useful.

If you are new here, this is also the easiest place to jump in. You do not need a perfect spec. A short, practical comment is enough.

## What to share

- the problem or workflow you want ClawWork to handle better
- why it matters to you
- what "good enough for v0.1" would look like
- links, screenshots, examples, or related issues if you have them

## Good topics for this thread

- task and session workflow
- artifact and workspace management
- gateway connection and remote OpenClaw support
- setup, onboarding, and installation experience
- UI polish and daily quality-of-life improvements
- platform support and integrations

## A few simple rules

- one comment per idea makes it easier to track patterns
- if a similar request already exists, link it or react with 👍 instead of duplicating it
- if your idea becomes a concrete feature request, feel free to open a dedicated issue and link it here
- small suggestions are welcome too - they often make the biggest difference in a v0.1 release

We will use this thread to understand demand, spot recurring pain points, and decide what belongs in the first public ClawWork v0.1 release.

Thank you for helping shape ClawWork early. Friendly, practical feedback is extremely valuable right now, and we genuinely want to hear what would make this tool more useful for you.

Use the comments in this issue as the starting point; group recurring requests across task and session workflow, workspace management, gateway connections, setup, UI, and integrations. Done means selecting a concrete v0.1 scope and moving accepted ideas into dedicated feature issues with a practical definition of good enough.

Written by the indexing model from the issue text.