@flowriki/agent 0.1.0-beta.27 → 0.1.0-beta.29

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -25,6 +25,30 @@ npx @flowriki/agent@latest doctor # diagnose setup problems
25
25
  npx @flowriki/agent@latest disconnect # forget this computer's credential
26
26
  ```
27
27
 
28
+ ## Write tests with Claude
29
+
30
+ The agent is also an MCP server, so Claude Code or Claude Desktop can write
31
+ Flowriki tests for you, on your own Claude plan. Claude drives a browser on
32
+ this computer, each step is performed before it is kept, and what it writes is
33
+ saved to a **new branch** for you to review and publish in the dashboard.
34
+
35
+ Connect this computer first (`connect` above), then add Flowriki to Claude:
36
+
37
+ ```
38
+ claude mcp add flowriki -- npx -y @flowriki/agent@latest mcp
39
+ ```
40
+
41
+ For Claude Desktop, add this to its MCP settings (`claude_desktop_config.json`):
42
+
43
+ ```json
44
+ { "mcpServers": { "flowriki": { "command": "npx", "args": ["-y", "@flowriki/agent@latest", "mcp"] } } }
45
+ ```
46
+
47
+ Then ask, for example: *"Write a Flowriki test that signs up and verifies the
48
+ email"*. Claude reads your project's features, sign-in profiles and helpers,
49
+ and uses them. You do not run `mcp` yourself — Claude starts it. It works
50
+ alongside `start`, in a browser window of its own.
51
+
28
52
  ## What you do not need
29
53
 
30
54
  No checkout of Flowriki, and nothing to build. `connect` and `start` are the