Results for “session”

Hunt Session Management vulnerabilities — session fixation (no regeneration on login), insufficient invalidation on logout / password-change / email-change, predictable or low-entropy session IDs, JWT-as-session with no exp/revocation, refresh-token rotation/reuse-detection gaps, OAuth/SSO session linkage, device-bound-session (DBSC) downgrade, and cookie attribute issues (Secure/HttpOnly/SameSite/__Host-). Validate with TWO real sessions (attacker A + victim B), body-diff every 200, and OOB confirmation for theft chains. Medium to Critical (fixation→admin hijack, no-invalidation→persistent ATO).

The English summary is being prepared. Showing the original description.

Save an agent session’s state, settings, memory, and task progress, then restore it in another conversation. List saved sessions, inspect their details, and remove old ones when managing checkpoints for ongoing work.

• Pause work and resume it in a later conversation
• Save progress checkpoints during long tasks
• Inspect saved sessions and their details

Identify individual sessions with unusually high or low spending using the median and MAD, a measure of spread around it. Filter by time period, adjust detection thresholds, and optionally return a failure exit code for automated checks.

• Find sessions with unusually high spending
• Check sessions with unusually low spending
• Review spending anomalies over the past week

Prepare a repository for Claude Code on the web by creating a startup hook that installs project dependencies. Register the hook and check that it runs successfully, along with a sample test and code quality check.

• Prepare a repository for Claude Code on the web
• Install dependencies when a web session starts
• Check that tests and code quality tools can run

Analyze Antigravity coding session artifacts to explain scope changes, repeated rework, and underlying causes. Produce an evidence-based report with confidence levels, prompt assessments, recurring problem areas, and prioritized recommendations for improving future development sessions.

• Reviewing sessions with repeated rework
• Separating scope changes from agent and codebase problems
• Finding files and subsystems associated with recurring friction

Create a disposable Herdr session to reproduce terminal, process, API, or agent issues separately from the main session. Drive tests through the CLI or API, collect evidence of state changes, and clean up the temporary session afterward.

• Reproducing pane, terminal, or process issues in Herdr
• Checking agent detection and permission-related state changes
• Collecting commands, logs, and state for a reproducible bug report

Automate page interactions and screenshots with agent-browser running in AWS Bedrock AgentCore cloud browsers. Use standard browser commands, preserve login state across sessions with persistent profiles, and watch active sessions through an AWS Console link.

• Run browser automation on AWS
• Reuse login state across browser sessions
• Watch a cloud browser session live

Summarizes the current Claude Code conversation into an evidence-backed map of goals, changes in direction, completed outcomes, current work, and open decisions. Use it to regain context after interruptions, session switching, or conversation compaction.

• Regaining context after switching sessions
• Reviewing progress after conversation compaction
• Identifying decisions that still need user input

Delete stored context-mode data for one session or an entire project after confirming the scope. Remove an unwanted session while preserving others, or clear project knowledge, session records, and statistics for a fresh start.

• Remove data from one unwanted session
• Clear a project database containing outdated information
• Reset all stored project data for a fresh start

List Git commits linked to agent work sessions, with branch or repository filters. See each commit’s message, date, linked sessions, and observation counts to review recorded changes alongside their session context.

• Review recent commits linked to agent sessions
• Filter linked commits by branch
• Review linked commits for a specific repository

Summarize recent agent sessions for the current project, grouped by date with highlights from recorded observations. Review today, the last seven days, or a chosen number of sessions, with totals for sessions, days, and observations.

• Review today's agent work
• Recap project activity from the last seven days
• Summarize a chosen number of recent sessions

Track multiple Claude sessions working on one project, check that changes reached main with screenshots and changelog entries, verify the live site, and identify finished sessions, interrupted work, and questions awaiting the user.

• Reviewing progress across parallel Claude sessions
• Checking merged changes, changelog images, and the live site
• Archiving finished sessions after preserving screenshots

Use when the user wants to browse, inspect, create, or update exploratory testing sessions in TestDino — by state, status, session type, assignee, release, or tags. Covers list_sessions, get_session, create_session, and update_session. Accepts counter-style IDs like SES-12.

The English summary is being prepared. Showing the original description.

Drive Codeman, the session manager this agent is running inside, over its HTTP API, from any agent CLI (Claude Code, Codex, Gemini CLI, OpenCode, Antigravity, Grok Build, DeepSeek Harness, OMP): list sessions, start worker sessions in any installed CLI, send them prompts, block until they finish (wait / wait-output / send-and-wait), read their output, and clean up; where available, message claude workers directly (Claude Code cross-session messaging). Use when asked to orchestrate or parallelize work across Codeman sessions, get a second opinion from another CLI or model, watch another session, or start and manage workers. Only usable inside a Codeman-managed session (CODEMAN_MUX=1); refuse to act otherwise.

The English summary is being prepared. Showing the original description.

Manage persistent coding sessions across Claude Code, Codex, Antigravity (agy), Cursor, and OpenCode engines. Use when orchestrating multi-engine coding agents, starting/sending/stopping sessions, running multi-agent council collaborations, cross-session messaging, ultraplan deep planning, ultrareview parallel code review, autoloop autonomous workspace iteration, ultraapp building deployable web apps from a structured Q&A interview, switching models/tools at runtime, exposing the orchestrator's 69 tools as an MCP server to Hermes Agent / Claude Desktop / Cursor / Cline / Continue / Zed / Windsurf / Goose, or running as an Agent Client Protocol (ACP) agent that Zed / JetBrains / Neovim / Emacs / VS Code / dsh can drive directly. Triggers on "start a session", "send to session", "run council", "ultraplan", "ultrareview", "autoloop", "ultraapp", "Forge tab", "build a web app", "one-click app", "AppSpec", "autonomous iteration", "iterate until goal", "deep paper review", "auto research", "switch model", "multi-agent", "coding session", "session inbox", "cursor agent", "opencode", "mcp server", "clawo-mcp", "hermes mcp", "model context protocol", "ultracode", "dynamic workflow", "fanout", "fan-out", "best-of-N", "steer turn", "interrupt turn", "fork thread", "rollback turns", "acp", "agent client protocol", "clawo acp", "zed agent", "jetbrains agent", "external agent", "dsh subagent", "deepseek harness".

The English summary is being prepared. Showing the original description.

Serverless Aura Graph Analytics (AGA) GDS Sessions — covers GdsSessions, AuraGraphDataScience, AuraAPICredentials, DbmsConnectionInfo, SessionMemory, get_or_create, remote graph projection with gds.graph.project.cypher and gds.graph.project.remote, gds.graph.project.native, gds.graph.construct, graphdatascience client 2.0 session endpoints, async compute and gds.jobs, AuraDB Cypher API memory/sessionId projection, algorithms, write-back, and session lifecycle. Use for AuraDB-connected, self-managed Neo4j, or standalone DataFrame/Spark session workloads. Does NOT cover the embedded GDS plugin on Aura Pro or self-managed Neo4j — use neo4j-gds-skill. Does NOT handle Cypher authoring — use neo4j-cypher-skill. Does NOT cover Snowflake Graph Analytics — use neo4j-snowflake-graph-analytics-skill.

The English summary is being prepared. Showing the original description.

Render a dashboard of the current Claude Code session — message counts, token usage, cache read/write, dollar cost, context %, lines changed, cost-per-turn sparkline, and a tool-call histogram — parsed from the session transcript JSONL by a bundled bash script. One bash call, zero analysis, zero confirmation. Optionally pass a session id to inspect a different session. Use when the user asks for session stats, usage, token or cost breakdown, or a session dashboard.

The English summary is being prepared. Showing the original description.

Use when ending or pausing a Claude Code session whose work must continue in a fresh session — user says "create a handoff", "write a handoff", "I'm ending this session", "prepare for a fresh session", "hand this off", or "/handoff" — or when starting a session in a project that already contains a HANDOFF.md at the root ("resume", "pick up where we left off", "continue from the handoff"). Also relevant when a session shows degradation symptoms — Claude contradicted an earlier decision, re-explored something already established, hallucinated file contents, or the user says the session "feels off", "is getting confused", or "context is running low".

The English summary is being prepared. Showing the original description.

Guides a user from "I want to watch recordings but don't know which ones" to a short, high-signal list of sessions worth watching. Use when the user asks which sessions or replays to watch, wants help finding interesting / useful recordings, says they don't know where to start in session replay, or wants to watch sessions about a goal (signup, pricing, onboarding, checkout, a feature, rageclicks, errors, mobile, a specific person) without naming exact filters. Turns a vague intent into a focused RecordingsQuery via `query-session-recordings-list`, then deep-links the best few and hands off to `investigating-replay`. Do NOT use when the user already has a recording/session ID (use investigating-replay) or wants the replay for a known error issue (use finding-replay-for-issue).

The English summary is being prepared. Showing the original description.

Load bounded working context at the start of a coding session. FIRES ON EVERY FIRST USER MESSAGE in a fresh session, regardless of content — including bare greetings ("hi", "hello", "hey"), task-only openers, or "let's start". Also triggers on: "fresh session", "session start", "first message in a new thread", "new chat", "cold start", "begin work in this repo", "starting work", "continue from prior session", "what were we working on", "resume", "what happened last time", "load memory", "recall context", "create a handoff", "prior session context", "latest handoff", "current state", "decision context". Skip ONLY if the user explicitly says "fresh start" or "ignore prior context". Self no-ops if invoked mid-session when context is already loaded.

The English summary is being prepared. Showing the original description.

Organize sessions and layouts in the OpenClaw Control UI, build session dashboards, and investigate display or connection problems. It covers connected clients and Gateways accessed directly or through Tailscale, with checks of both saved state and rendered screens.

• Group and pin sessions for easier navigation
• Build a dashboard within a dedicated session
• Arrange dashboard tabs and widgets

Capture token usage from Claude Code session logs, calculate USD costs using the supplied pricing reference, and save structured records to AgentDB. Review totals by model and tier, and provide data for cost reports.

• Record costs after a block of work
• Save final usage totals at session end
• Capture usage periodically during long sessions

Break down a Claude Code session's costs by assistant message to find expensive responses. Compare input, output, cache writes, cache reads, and models, with message cost percentiles providing context for investigating unusually costly activity.

• Investigate messages in a flagged session
• Check the cost contribution of cache writes
• Review expensive messages after a specific time

Check opencode commands, HTTP server behavior, lifecycle events, and terminal startup with purpose-built scripts. Find stored sessions by ID, title, or scoped message searches, and export conversations as JSON for further inspection.

• Check CLI commands and HTTP server health
• Observe lifecycle events associated with plugin hooks
• Check terminal startup and keyboard input