DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check whether a site connection is still signed in with Hycli

Run a health check without AI that separates signed-out, changed, blocked, and unreachable sites.

Credentials. Session import reads only the target domain's cookies and storage, and those secrets stay in your local vault.

Who it is forA user with several logged-in sites wired into agents who needs to know why an action stopped working.

The problemWhen a login expires, agents can waste tokens retrying, and the real cause is not clear.

The outcomeA status that tells you whether to reconnect your account, repair the spec, or wait.

What you need first

  • A Hycli release package for Windows, macOS, or Linux (Rust and Node.js are not needed to run it)
  • An AI connection: an OpenAI, Anthropic Claude, xAI, or Z.ai API key, or a local ChatGPT Codex login
  • The URL of the target website and a short goal for it
  • An MCP client such as Claude Code, Cursor, or Codex, if your agent will call Hycli

Steps

  1. Run hycli open, go to Accounts, and click **Find my sign-in** for the logged-in site.
  2. Run hycli check your-website to replay verified read chains. (inferred, check the README)
  3. If the status is signed_out, reconnect the account from the dashboard.
  4. If the status is site_changed, run hycli prepare https://your-website.example --intent "..." again with the same goal to refresh the spec. (inferred, check the README)
  5. If the status is blocked or unreachable, wait and run hycli check your-website again later. (inferred, check the README)

Prompt for your agent

Using the Hycli repo, run `hycli check <site-name>` and report the status it returns: signed_out, site_changed, blocked, or unreachable. Expected output: one status and no LLM call. Verify the status before reconnecting an account or re-preparing the site.

Caveat. The check reports a status but does not fix signed-out accounts or changed sites on its own.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page