awslabs / awslabs/cli-agent-orchestrator

[Feat]Agents do not get cleaned up.

Open
#89 1 comment 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
1.3k
Forks
267
Avg merge
1d 23h
Merged PRs (30d)
70

Description

## Overview
Using an orchestrator with 28 agents under him.
While doing his tasks multiple agents are spanned (even the same agents) in tmux sessions.
These will not be cleaned up. At the end of the process we might have literally a hundred agent windoes

## User Stories
- As a user, I want to be able to close agent session windows, so that i have less complexity in the tmux windows.
- As a user, i want the system to get rid of unused window periodically

## Acceptance Criteria
- When configured for a certain time t1, all agent windows that are inactive for t>t1 are [closed](url)

## Proposed solution

[tmux-cleanup-README.md](https://github.com/user-attachments/files/25580387/tmux-cleanup-README.md)
[tmux-cleanup.sh](https://github.com/user-attachments/files/25580386/tmux-cleanup.sh)

See attached files

Contributor guide

Open the contributing guide

Research direction

Start by reading the attached tmux-cleanup-README.md and tmux-cleanup.sh, then locate how the orchestrator creates and tracks agent tmux sessions. Implement configurable cleanup for windows inactive longer than the selected threshold, and verify that inactive windows are closed without affecting active agents.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, shell
Domain
cli, devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.