Difficulty managing multiple sessions and agents across different platforms and interfaces

Signals over time

3 observed signals across 1 sources, tracked for 0 days. Confidence: low.

What people are saying Observed

• “Your other comment is flagged as dead so I'll reply here: > I like the idea of using a “local inbox for agent sessions” because switching between different contexts can be more frustrating than the actual time it takes the agent to run. > But I’m curious about how you see the inbox being useful beyond simply storing and replaying conversations. > A few things would help me understand the practical value: > What does a session actually contain? Is it just the conversation, or does it also include things like prompts, code changes, test results, Git commits, and other context? Can you reliably replay a session? Ideally, someone should be able to see what task was given, what the agent changed, what tests were run, and whether the task actually passed. What happens when work gets interrupted? If I pause one task and start another, can I come back later without losing the context or putting the project into a confusing state? How do you prove the work was completed? For example, can the system show the tests that were run, the changes made, and whether they passed? How is everything kept safe? If everything runs locally, that's great, but I'd still want to kn”

  Hacker News · question

• “With six agents running, the slow part was me noticing which one had stopped. I love Cursor, but not using Claude Code and Codex with heir crazy generous subsidized subscriptions would be a mistake. So I run five or six Claude Code and Codex sessions at a time, across 4 Cursor windows and a WSL box. Nothing was ever wrong with the agents. One of them would ask “can I run this Bash command?” at minute three, and I would find out at minute forty, by walking through terminal tabs. So I built a sidebar that does the walking, it’s basically agent view but for all agents, not just the Cursor ones. This is it on a normal afternoon: api-server 🔔 fix flaky auth test 3m · Claude needs your permission to use Bash ⟳ migrate billing tables 2m ⚙3 · Migrating schema web-app 🟡 redo settings page 12m · Done. The form now saves on blur and ⟳ bump deps 4m ❯ build-box infra ○ terraform plan review 1h ❯ (Text can’t show the icons properly. The bell is red, the fourth row is a Codex session, and build-box is another machine.) It’s called SessionDeck. One row per running Claude Code, Codex or Cursor agent session, grouped by project. Click a row and you are in that tab or terminal (for a tmux or SSH se”

  RSS Feeds · frustration

• “As I started to use `claude` and `codex` more it became too hard to manage all the sessions across all my tmux panes and sessions, so I built Puppet Master. I see now there is quite a lot out there now for managing agents to write software, but a) I started working on this before a lot of them, and b) there are things in Puppet Master that just don't exist all in one product. For me I'd say the highlights are: 1) Web instead of terminal -- it's just a richer interface 2) iOS app so I can keep working on things from anywhere 3) Local + Remote workers (heterogeneous fleet), I work on things that are cross-platform and PM lets agents spawn across the fleet depending on workload needs. 4) Connections - first-class support for integrating MCP and REST API (ala OpenAPI definitions) into your agents. This goes above and beyond what a single harness can do via i.e an MCP integration. PM imports it (scoped to a bucket/project) and associates it to a policy. It lives between the agent and the remote MCP/API and enforces a policy. My normal flow is give full read access to agents and any APIs that do writes, approval needed. PM has native approval UI on web AND mobile”

  Hacker News · request