syntaqxEnding a session by hand is a soft close: like one that timed out, it comes back the moment its harness is heard from again. An update or a recorded entry now brings it back, where before both were refused with 'This session has ended. Start a new one.' A start already did. So a harness that was still running picks up where it was, and one that is truly gone stays ended. A session its harness ended itself still stays ended. g1t_contracts::work::revives(end_reason) is the one rule, for timed_out and 'ended by hand by @…', and update, record and subagents' late hooks use it. The End session dialog and the sessions guide say so. Checked: cargo test -p g1t-contracts (322, new: what comes back when heard from), -p g1t-work (214), cargo check -p g1t-work (wasm32).de2b3aeHistory
- ..
- about.ts
- access.ts
- account-deletion.ts
- accounts.ts
- actions.ts
- advisories.ts
- agent-sessions.ts
- agents.ts
- ai.ts
- audit.ts
- billing.ts
- chat-markdown.test.ts
- chat-markdown.ts
- chat.test.ts
- chat.ts
- checks.ts
- clients.ts
- codeowners.ts
- coding-agents.test.ts
- coding-agents.ts
- compute.ts
- connectors.test.ts
- connectors.ts
- d1.test.ts
- d1.ts
- datasets.fixtures.json
- datasets.test.ts
- datasets.ts
- deploy-keys.ts
- deployments.ts
- discovery.test.ts
- discovery.ts
- docs.ts
- events.ts
- folios-dashboard.ts
- folios-design.ts
- folios-slides.ts
- folios.fixtures.json
- folios.test.ts
- folios.ts
- github.ts
- guardrails.ts
- identity.ts
- ids.test.ts
- ids.ts
- inbox.ts
- index.ts
- instances.ts
- integrations.ts
- members.ts
- names.test.ts
- names.ts
- notify.ts
- oauth.ts
- og.ts
- packages.ts
- people.ts
- platform.ts
- privacy.ts
- projects.ts
- rate-limits.ts
- repos.ts
- result.ts
- rules.ts
- runners.ts
- scopes.ts
- search.ts
- security-suite.ts
- security.ts
- sounds.ts
- status.ts
- teams.ts
- telemetry.ts
- updates.ts
- webhooks.ts
- work.ts