Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Automations: run a real recurring job for a week and check it stays useful

Aperta
  • Qualcosa non va?
#175 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
Più di una settimana
Idoneità per principianti
58/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Ambito
ai, testing

Direzione di ricerca

No code change is involved. Sign up at app.useagent.org, create one recurring Automation with clear instructions, and let it run at least five times. Done means a single report comment on this issue with links to your session threads, what worked, what broke, and what you automated and how often. File any bug as a separate issue and link it.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

feedback

Check whether an automation stays useful over several runs.

Try this

  1. Pick something you'd want every day or week: a digest of a topic you follow, new releases of an open-source project you use, or new posts on a blog.
  2. Create it in Automations with clear instructions: what to check, what to write, how long, and "say nothing new if nothing changed".
  3. Turn it on and let it run at least five times.
  4. Read each result. Change the instructions once if something annoys you.

What to look for

  • Results stay accurate and on topic, and links work.
  • It doesn't repeat the same items run after run.
  • It says "nothing new" when that's true, instead of padding.
  • Failed runs are easy to spot.
  • What would make you keep it running.

Your report

Post one comment here with:

  • Links to your threads (app.useagent.org/session/...)
  • What worked
  • What broke or confused you, and what you expected instead
  • Screenshots or a short screen recording
  • What you automated and how often

Open a separate bug issue for anything broken, with the steps to reproduce it, and link it in your comment.

No need to claim; post your report as a comment.

General asks

  • Do the steps yourself in the hosted app. Sign up with your email at app.useagent.org; you don't need an API key or a card to start. The link in the sign-up email works for 24 hours, so check spam if it's missing.
  • Run everything by hand. Reports from runs done or simulated by another AI tool get closed.
  • Use made-up details, test accounts and data you own. Don't point the agent at other people's accounts, inboxes or private data, and don't send real forms or messages to strangers.
  • More than one person can report on the same issue, and every report helps. If someone already found what you found, add only what's different.
  • Stuck? Comment here with a screenshot and we'll help.

Keep private details out of here

This page is public. Don't post your real email, phone number, address, API keys, or screenshots that show any of them; blur them first. Send anything private to [email protected] with a link to your comment here.

Using AI tools, and what gets no reply

  • AI help is fine. Blind AI output is not. You must understand every line you submit, run it yourself, and show it working in the app with your own screenshots or recording.
  • Pull requests that look generated and untested get closed without a reply and labeled spam, which also means they don't count for Hacktoberfest. Signs we look for: no proof from a real run, code that ignores this repo's patterns or reinvents helpers that already exist, unrelated files changed, a description that only restates the issue, and failing checks nobody looked at.
  • One pull request per issue, by the person who claimed it. Opening pull requests on issues someone else has taken, or several near-identical pull requests for the same bounty, counts as farming and gets the same treatment.
  • Bounties are paid only for the verified outcome the issue describes (for example, a workshop that actually happened, or an app that works on both systems), never for a write-up, a plan, or an unfinished attempt.
  • When we ask a question in review, answer it in your own words. If you can't explain your change, we can't merge it.
Lingua principale
TypeScript
Stelle
371
Fork
78
Merge medio
2g 2h
PR unite (30g)
44

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di useagenthq/useagent

Tutte le issue di useagenthq/useagent

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.