You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,9 +12,7 @@ Your agent will be able to use this MCP server to talk to your running Rails app
12
12
13
13
This MCP server is an open-source component of [Tidewave](https://tidewave.ai), the agentic development environment for Rails and Phoenix.
14
14
15
-
You can use this project as a standalone MCP server or integrated with the [Tidewave product](https://tidewave.ai).
16
-
17
-
To use it as a standalone MCP server, follow the installation instructions below.
15
+
You can use this project as a standalone MCP server or integrated with the [Tidewave product](https://tidewave.ai) by following the instructions below.
18
16
19
17
## Installation
20
18
@@ -117,6 +115,10 @@ Also, because it resolves the location from your running app instead of parsing
117
115
118
116
## Troubleshooting
119
117
118
+
### The Tidewave toolbar is missing
119
+
120
+
This may happen if you are compressing your responses (gzip, brotli, etc) after the Tidewave middleware runs. Use `bin/rails middleware` and make sure Tidewave comes after `Rack::Deflater` or similar. Also look into your browser and terminal logs for any errors.
121
+
120
122
### Using multiple hosts/subdomains
121
123
122
124
If you are using multiple hosts/subdomains during development, you must use `*.localhost`, as such domains are considered secure by browsers. Additionally, add the following to `config/initializers/development.rb`:
@@ -135,7 +137,7 @@ The above will allow your application to run embedded within Tidewave across mul
135
137
136
138
### Content security policy
137
139
138
-
If you have enabled Content-Security-Policy, Tidewave will automatically enable "unsafe-eval" under `script-src` in order for contextual browser testing to work correctly. It also disables the `frame-ancestors` directive.
140
+
If you have enabled Content-Security-Policy, Tidewave will automatically enable "unsafe-eval" under `script-src` in order for contextual browser testing to work correctly. It also disables the `frame-ancestors` directive. This is done only in the environments that Tidewave is loadead (development by default).
139
141
140
142
### Production Environment
141
143
@@ -161,6 +163,8 @@ The following config is available:
161
163
162
164
*`team` - set your Tidewave Team configuration, such as `config.tidewave.team = { id: "my-company" }`
163
165
166
+
*`toolbar` - controls whether the Tidewave toolbar is injected into HTML pages. Defaults to `true`
167
+
164
168
## Acknowledgements
165
169
166
170
A thank you to Yorick Jacquin for the initial version of this project.
0 commit comments