Add Synaspe Project

[JJC3321]

Synapse gives your AI agents hands. It's a developer platform for defining, testing, monitoring, and managing web automation actions powered by the TinyFish execution engine.

Try Here

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[simantak-dabhade]

🔶 Security: committed Supabase credentials — please rotate and scrub

This PR commits synapse-main/.env with Supabase project credentials:

VITE_SUPABASE_PROJECT_ID="hclfbztkexgknfgbgtbi"
VITE_SUPABASE_PUBLISHABLE_KEY="eyJhbGci...NKI2hY"
VITE_SUPABASE_URL="https://hclfbztkexgknfgbgtbi.supabase.co"

The VITE_* prefix means these are intended to be bundled into client code, and the key's decoded role is anon — so this is a Supabase anon (public) key, not the service-role key. That makes it much less catastrophic than a raw service-role leak, but it's still a problem to have it committed to a public repo:

1. Your Supabase project URL and anon key together identify a real project tied to your organization.
2. Anon keys rely on Row Level Security being correctly configured. If RLS has gaps on any table, any reader of this repo can hit those tables directly.
3. Rate limits, usage quotas, and billing are tied to that project.

Please do the following:

1. Rotate the anon key in your Supabase dashboard (Project Settings → API → roll the anon key). Also check RLS on every table in this project.
2. Delete synapse-main/.env from this PR branch.
3. Add synapse-main/.gitignore covering .env, .env.local, .env.*.local, node_modules/, .next/, dist/.
4. Force-push to rewrite history so the credentials are not in the branch log.
5. Add a synapse-main/.env.example with just variable names and placeholder values (no real values) so future contributors know what to fill in.

Reopening for a full review once the credentials are rotated and scrubbed from branch history.

Context: we're currently tightening up secret hygiene across the cookbook after another contributor leaked a TinyFish API key in a similar way. A repo-level .gitignore is being added to prevent this class of issue going forward.