Public issues and requests
Open an issue at github.com/Wy2926/nodelane-act/issues. Search for an existing report first, then describe the expected and actual behavior. Community support does not include a promised response time or service level.
- NodeLane Act, operating system, browser, and Node.js versions.
- AI client, installation method, and whether the extension reports a connection.
- Site, operation name, minimal redacted arguments, error code, and reproduction steps.
- For writes, whether you checked the final state on the website. Do not repeatedly publish or delete content just to reproduce a problem.
Private contact
Send account-related details, privacy requests, and security reports to [email protected]. Maintainers and the email service process your message. Share only what is necessary to resolve the issue.
Do not send passwords, cookies, full session tokens, bridge authentication files, or unredacted network captures. Screenshots and logs can reveal usernames, private messages, content, and paths; review them before sharing.
First checks
Confirm Node.js 22+ runs, the absolute MCP path exists, and MCP and the browser run on the same computer. Check that the extension is enabled, has website permissions, and that the website session is signed in.
After navigation errors, select the page again. After a write timeout or disconnection, inspect the website outcome first. Complete verification normally instead of repeatedly retrying restricted requests. See act.nodelane.net/en/docs/ for installation instructions.