useagenthq/useagent

People who help build UseAgent should be seen. Add a contributor wall to the README that thanks everyone who contributes: code, docs, design, tests, translations, bug reports and testing reports. Where to start The all-contributors spec: a .all-contributorsrc file plus a marked section in README.md. Run its CLI with bun (bunx all-contributors-cli), not npm; this repo uses bun only. Put the section after "Hacktoberfest 2026" and before "Community" in README.md. Seed it from merged pull requests and accepted reports on #112 to #117, with the right contribution type for each person (code, doc, design, test, translation, bug, ideas). Done when The README shows the wall, with avatars and links, for everyone who has contributed so far. CONTRIBUTING.md says in two lines how a new contributor gets added. The pull request lists who you added and why. Maintainers then install the all-contributors bot, so later additions are a one-line comment. Try the app first (5 minutes, free) Open https:

On a new account the Dashboard's recent runs table just says "No runs yet." and stops. Give that empty state a way forward: a short line and a button that starts a first task. Where to start frontend/components/dashboard/recent-runs-table.tsx, the runs.length === 0 branch. New tasks start at /agent/new. Use the shared button in frontend/components/base/buttons/ and the scale in frontend/components/foundations/DESIGN-RAMP.md. Don't add a new style. Done when An empty dashboard shows one line of copy and a button that opens /agent/new. It works by keyboard, reads right to a screen reader, and looks right in light and dark themes and at phone width. A test covers the empty branch. Try the app first (5 minutes, free) Open https://app.useagent.org/login?ref=hacktoberfest and sign up with your email. Signing up costs nothing. Check your inbox for the mail from UseAgent and click the link. It works for 24 hours. Not there? Look in spam. Sign in. The model at the bottom says GLM 5.3, Free

When someone builds something with UseAgent, the next person should be able to find out how. Make a small "Built with UseAgent" badge that any project can drop into its README, plus a docs page that explains how to use it. Where to start Put the badge SVG at docs-site/public/badges/built-with-useagent.svg. Start from the mark in docs-site/public/useagent-mark.svg and the shields style the README badges already use. Make a light and a dark version, or one that reads on both. Add a docs page at docs-site/docs/getting-started/badge.mdx and list it in that folder's meta.ts. What the docs page shows A Markdown snippet and an HTML snippet that load the badge from https://raw.githubusercontent.com/useagenthq/useagent/main/docs-site/public/badges/built-with-useagent.svg and link to https://app.useagent.org/login?ref=<your-project-name>. An "Open in UseAgent" link: https://app.useagent.org/agent/new?prompt=<your task, URL-encoded> opens the New thread page with that task typed in. Signed-out

A brand-new account opens on "What do you want done?" and an empty box. Many people don't know what to ask an agent the first time and leave. Show a few starter tasks under the composer until the person has run something. Where to start frontend/app/(workspace)/agent/new/page.tsx: under the composer, only "Recent tasks" renders, and only once you have runs. For a new account nothing shows. The page already reads ?prompt= and passes it to NewTaskComposer as initialPrompt, so a starter can fill the composer without any new state plumbing. Follow the look of the Recent tasks list just below it, and the type and colour scale in frontend/components/foundations/DESIGN-RAMP.md. Done when With no runs, 3 or 4 starters show, each a short plain sentence that works on the free GLM 5.3 model. For example: a one-page portfolio site with a link to it, a comparison table from a web search, a 5-slide deck on a topic, a clean-up of a CSV file. Clicking one puts its text in the composer, ready to edi

Open three threads in three tabs and every tab reads the same thing: "UseAgent - one interface for every coding agent". Name each tab after what's in it, so people can find their work again. Where to start frontend/app/session/(thread)/[id]/page.tsx (threads) and frontend/app/(library)/agent/artifacts/[id]/page.tsx (artifacts) have no title of their own. runTitle() in frontend/components/chat/types.ts already turns a prompt into a short title; the Recent tasks list on the New thread page uses it. React 19 lets a component render <title>, or you can use Next's generateMetadata. Pick one, and don't fetch the thread twice to do it. Done when A thread tab reads like Fix the login bug - UseAgent, and follows the thread if it gets renamed. An artifact tab shows the artifact's name. Long titles are cut short sensibly, and a thread that fails to load keeps the generic title. Try the app first (5 minutes, free) Open https://app.useagent.org/login?ref=hacktoberfest and sign up with your ema