Skip to main content
Every install in these docs comes down to a few lines of code in a known place. If you work with a coding agent, it can do those steps for you. All it needs is your project ID and a way to read these docs.

​
Copy the prompt from your dashboard

Every project has a prompt written for coding agents under Settings → Install. It already contains your project ID and the steps for your platform, so you can paste it into the agent as is. When the agent is done, read through what it changed before you ship. The quickstart for your platform shows what a correct install looks like, and the two should match.

​
How agents can read these docs

  • Context7. These docs are indexed from the public FeddyLab/feddy-docs repository. If your agent has the Context7 tool, it can look up feddy directly.
  • llms.txt. feddy.app/docs/llms.txt lists every page with a one-line summary, and feddy.app/docs/llms-full.txt is the full text of every page in one file. Paste either link into the agent’s context.
  • The SDK source. The iOS package at FeddyLab/feddy-ios is public, so an agent can read the code behind every call these docs mention.

​
What to check afterwards

Three things tell you the install is right:
  • Feddy is set up once, with your project ID, when the app or page starts and before anything else can open it.
  • The Support button is somewhere users already look for help, usually Settings.
  • A message sent from a debug build shows up in your inbox, and your reply from the inbox shows up in the app.
If all three hold, you’re done. Everything else, from identifying users to the unread badge, is optional.

​
Next steps

Identify users

Tell Feddy who’s logged in, so you see their name in the inbox and replies can reach them by email.

Unread badge

Show a count on your Support button so users notice when you’ve answered.