Split the Files panel view from its fetching and test each state #348

The Files panel next to a thread has no tests, and because its 5-second background refresh reuses the manual refresh path, the refresh button spins and switches off every 5 seconds while a task runs.

Where to start

1. In frontend/components/chat/artifacts-rail.tsx, load() sets the refreshing state both for the 5-second poll and for a click.
2. Track a manual refresh separately so only a click spins the icon, and move the markup into a small view component that takes the state as props.
3. Add render tests for the loading, empty, unavailable and list states and for the spinner showing only on a manual refresh.

Code to look at:

• frontend/components/chat/artifacts-rail.tsx:39
• frontend/components/chat/artifacts-rail.tsx:67
• frontend/components/chat/artifacts-rail.tsx:85
• frontend/components/chat/artifacts-rail.tsx:94

Done when

• While a task runs, the refresh icon stays still unless clicked.
• New tests cover the four states and the spinner rule.
• bun test components/chat passes.

Free to try

Sign up free at app.useagent.org. New accounts get free model credits (GLM or Claude Opus, up to a limit) and free cloud sandbox time, enough to finish this task without paying or adding a key.

Send it a small task in plain words and watch it work. You'll see the screens this issue is about. The link in the sign-up email works for 24 hours. Not there? Check spam.

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, payment details, API keys, or screenshots that show any of them. Send anything private, including how you'd like to be paid, to [email protected] with a link to your comment here.

Claim it

Comment /take and the issue is assigned to you. First come, first served.

Rules

• Use the app while you work, and put before and after screenshots or a short recording in your pull request. For backend or docs work, show the result end to end.
• One change per pull request. Run the checks in CONTRIBUTING.md.
• AI help is fine, blind AI output is not. You must understand, run and explain every line you submit.
• Untested or generated pull requests, and pull requests on an issue someone else claimed, are closed without a reply and don't count for Hacktoberfest.