Nango is the integration platform where coding agents build integrations. Engineers, or coding agents like Claude Code, Cursor, and Codex, write integrations as code in your repo, and Nango’s cloud runtime runs them securely and at scale. - Source: dev.to / about 2 months ago

You will need a Nango account (the free tier is enough for development). Then register your own HubSpot OAuth app with the crm.objects.contacts.read scope, set the OAuth callback URL to https://api.nango.dev/oauth/callback, and configure HubSpot as an integration in the Nango dashboard. - Source: dev.to / 3 months ago

Nango is the only platform in this comparison that treats all three loops as first-class, and the only one where the same code an agent builds today runs unmodified in a hardened tenant-isolated runtime tomorrow. - Source: dev.to / 3 months ago

Nango | Full-time | Remote (North America, LATAM, Europe) | https://nango.dev Nango (YC W23) is a developer infrastructure company and the leading provider of API access for agents and apps. It enables AI applications to connect to the real world through integrations. More than 250 paying customers rely on Nango today, including Replit, Mercor, and Exa. We are a YC-backed,... - Source: Hacker News / 6 months ago

Nango fits teams that already have an agent stack and want OAuth and token handling done cleanly. - Source: dev.to / 6 months ago

There's a guide on the subreddit wiki on how to format code for display on reddit. When in doubt, you can also use GitHub Gist or Hastebin, though. Source: over 4 years ago

In future, use code formatting or put your code into hastebin.com and then post a link here. It will make it easier to read. Source: over 4 years ago

If you want to post a log, you'll have to generate one first (go to settings > logging and set both logging verbosities to 0-debug and 'log to file' to ON, then do whatever you need to do to create the offending behavior; that should make the log. Then, open the resulting log in a text editor and copy/paste the contents somewhere like hastebin.com and post a link to it here). Source: over 4 years ago

Close RetroArch, then navigate to your 'logs' folder in your RetroArch user directory (if you can't find it, open RetroArch and go to settings > directory and see where your 'logs' directory is located). You should see a text file there. Copy/paste its contents somewhere like hastebin.com and then post a link to it here and I/we can take a look. Source: almost 5 years ago

Can you give me the entire command history that got you to where you are now? If you can do that, make sure there is not personal information in the history, especially passwords. Look at the output of history. If it's large, try hastebin.com . Source: almost 5 years ago