Files and results
Sending files to an Agent, getting finished work back, and what happens to long-running jobs.
Sending files in
Attach a file to a message and Runva copies it onto the Agent's Computer to work with. The attachment belongs to the conversation, and the working copy lives on the machine.
That's two separate things on purpose. The conversation keeps a permanent record of what you sent, and the Agent gets a real file it can open, edit, and run.
A new Computer only restores files from Threads assigned to it. Moving an Agent to a different Computer doesn't bring the old machine's files along.
If Runva can't get a file onto the Computer, it says so and the work stops there. It won't carry on as though the file arrived.
Getting results back
When an Agent makes something for you, it hands the file back into the Thread where you can preview or download it. A path on a machine isn't a result, and an Agent that only tells you where it put something hasn't finished.
Anything it produced is also still on the Computer, so you can ask for a change without starting over.
Long-running work
An Agent can start something slow and carry on. When the process finishes, the outcome arrives in the conversation on its own, with whether it worked and what it printed.
The full log stays on the Computer for as long as the Computer does, so an Agent can go back and read the part that matters. Runva keeps a bounded number of recent logs per Computer, so anything that has to survive is worth copying somewhere permanent.