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

How to capture a TikTok video with its media as evidence with Jev Social

Read a selected TikTok video and save its media offline when your goal explicitly asks for it.

  • Research
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Who it is forA trust and safety or content analyst who needs a saved copy of a specific TikTok video with its metadata.

The problemVideo pages change or disappear, and a reviewer needs a stable record tied to the original URL.

The outcomeCaptured metadata, a downloaded MP4, and a poster image stored by socai, with the media intent kept in the operation history.

What you need first

  • Node 22 or newer
  • Chrome already signed in to Instagram, TikTok, or LinkedIn
  • An OpenRouter API key for the default decision provider
  • A current socai CLI (onboarding can install it on macOS and Windows; on Linux install it first and set it on PATH or SOCAI_BIN)

Steps

  1. Install Node 22 or newer and sign in to TikTok in Chrome.
  2. npx github:socai-io/jev-social#v0.1.13 onboard
  3. npx github:socai-io/jev-social#v0.1.13
  4. Write the goal so it explicitly requests an offline copy of the video, because media download runs only when the goal asks for it.
  5. Review the socai evidence and downloaded media, which are stored separately from Jev checkpoints, and delete only what you no longer need.

Prompt for your agent

Use the socai-io/jev-social repo to read the TikTok video at <url> and save an offline copy of its media, since the goal explicitly requests it. Expected output: metadata, an MP4, and a poster in the socai evidence store. Verify that the media download appears in the operation history and note any missing comments.

Caveat. A recorded TikTok run captured media successfully but comments were unavailable, so partial results are normal.

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