Skip to content

background commands requiring timeout to proceed #7

Description

@Sentdex

cant decide how insane I want to get with this, but long-running commands make you wait 120s for the timeout (ie: if you're serving a server or something, so it's a long-running command).

one option is purely just a sys prompt to tell it to always use nohup w/ a logfile.

another option is to use threading and a background task manager.

I eventually want to bring in subagents w/ task management, so maybe can do this together, but I kind of think we can solve the long running terminal commands from the agent with a simple nohup only.

mostly just putting here for my notes, but feel free to share an opinion.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions