Add AgentsView as an optional sessions integration

[yourconscience]

What

• add dotagents sessions as a thin launcher for agentsview serve
• keep AgentsView optional and independently installed
• support local browser suppression and SSH tunnel hints
• list AgentsView and HarnessKit together as supported integrations

Verification

• go test ./...
• local launch returned HTTP 200
• SSH launch on m4 returned HTTP 200

Summary by Sourcery

Add an optional sessions launcher that integrates AgentsView without making it a dotagents dependency.

New Features:

• Add the optional dotagents sessions integration for launching AgentsView session search, replay, telemetry, and usage views.
• Support local and SSH-oriented AgentsView launches with browser suppression, forwarded serving options, and tunnel guidance.

Enhancements:

• Document HarnessKit and AgentsView together as independently installed supported integrations, with clear ownership boundaries.

Documentation:

• Update CLI help, README, and the dotagents skill documentation with the new sessions command and integration guidance.

Tests:

• Add coverage for sessions argument parsing, serving options, port detection, missing-install guidance, and help behavior.

[sourcery-ai]

Reviewer's Guide

Introduces dotagents sessions as a thin, independently installed AgentsView integration, including forwarded serve flags, local browser suppression, SSH tunnel guidance, CLI registration, documentation, and focused tests; HarnessKit and AgentsView are now presented as supported optional integrations.

Sequence diagram for launching AgentsView locally

sequenceDiagram
    participant User
    participant Dotagents
    participant PATH
    participant AgentsView
    User->>Dotagents: dotagents sessions [flags]
    Dotagents->>PATH: exec.LookPath(agentsview)
    PATH-->>Dotagents: executable path
    Dotagents->>AgentsView: serve [--no-browser] [forwarded flags]
    AgentsView-->>User: Local session dashboard

Loading

Sequence diagram for remote AgentsView SSH launch

sequenceDiagram
    participant User
    participant Dotagents
    participant AgentsView
    User->>Dotagents: dotagents sessions --ssh-host user@host
    Dotagents->>AgentsView: serve --no-browser [forwarded flags]
    Dotagents-->>User: Loopback URL and ssh -L tunnel command
    User->>AgentsView: Open tunneled dashboard

Loading

File-Level Changes

Change	Details	Files
Add a new optional AgentsView launcher through the sessions command.	Parse launcher-specific flags while forwarding serve options unchanged. Check for the independently installed agentsview binary and provide an installation hint when absent. Invoke agentsview serve with inherited standard streams and suppress browser launch when requested or running remotely. Register sessions in command dispatch, help output, and CLI documentation.	cmd/dotagents/agentsview.go cmd/dotagents/main.go cmd/dotagents/cli_launch_test.go
Add remote-session launch guidance for local access over SSH.	Detect SSH sessions or an explicit SSH host. Print the remote loopback URL and an ssh -L tunnel command. Derive the SSH host when running inside an SSH connection and honor explicit host input.	cmd/dotagents/agentsview.go skills/dotagents/SKILL.md README.md
Document AgentsView alongside HarnessKit as an optional integration with separate ownership boundaries.	Describe AgentsView session search, replay, telemetry, usage, and independent index/configuration ownership. Document --no-open, remote usage, and forwarded serve flags. Present both integrations in a shared supported-integrations section.	README.md skills/dotagents/SKILL.md
Cover argument handling and launcher behavior with focused tests.	Test flag parsing, SSH validation, port extraction, browser suppression, missing-binary guidance, and help-output behavior. Update root help expectations for the new command.	cmd/dotagents/sessions_test.go cmd/dotagents/cli_launch_test.go

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: b722e48c-265b-408e-a597-a99fa1783402

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Needs a human reviewer. This adds a launcher for an external service that indexes and exposes local session transcripts, telemetry, and usage data. If the integration is wrong, an index or other local state may remain after reverting, but it is bounded and can be cleared or rebuilt; no money movement, deletion, or irreversible authorization change is introduced.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 54c408f193

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Honor the forwarded bind host in tunnel hints

When a remote invocation forwards a specific non-loopback bind address, such as --host 192.0.2.10, AgentsView listens on that address but this URL is always built with 127.0.0.1; tunnelCommand consequently forwards to localhost:PORT, where nothing is listening. Since the CLI help and documentation advertise --host ADDR, either derive the tunnel target from that flag or force AgentsView to bind to loopback in remote mode.

AGENTS.md reference: AGENTS.md:L49-L51

Useful? React with 👍 / 👎.