Skip to content

feat(cron): add ScriptContext.set_session_mode for cron sessions - #16681

Merged
bolichen97 merged 1 commit into
mainfrom
feat/cron-set-session-mode-16653
Oct 6, 2026
Merged

bolichen97 merged 1 commit into
mainfrom
feat/cron-set-session-mode-16653

Conversation

@hoang-phan98

@hoang-phan98 hoang-phan98 commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: A script cron can set the approval mode of a dashboard session it opened, to trust or trust_reads, so unattended work in that session does not wait on each tool prompt.

A script cron can open and seed its own dashboard session with the four ScriptContext methods #16398 added, but it cannot set that session's approval mode. The new session then stops at the first tool approval with nobody at the keyboard. Issue #16653 records the gap and the approved shape: a fifth method, ScriptContext.set_session_mode(slot, mode).

Why it matters

Every dispatcher cron that opens a worker session today produces a session that stalls on its first tool call. Left alone, authors will reach for a wider credential to set the mode, which is the escalation #16398 refused on purpose.

Not a goal

  • yolo or normal for a cron. yolo is the process-global grant and normal is the off-switch at any scope; neither is a creation-time posture for one unattended session.
  • Letting a cron set the mode of a session it did not open.
  • Any change to how the owner, the dashboard UI or an app token sets a mode.
  • Per-agent tool pre-approval, or any change to the approval_modes governance scope.
  • Letting a cron child mint a dashboard token. The mint refuses it as before.

What changed (motivation → approach → change)

Piece What it does
ScriptContext.set_session_mode(slot, mode) in cron_script.py POST /api/chat/mode with {slot, mode} and the cron's own credential; returns {ok, mode}; raises RuntimeError carrying the gateway's code on a refusal
/api/chat/mode in _CRON_SESSION_CONTROL_PATHS (dashboard/handlers/_shared.py) the switch mirror from #16398 refuses a cron: key on the mode route with 403 session_control_disabled while agent.session_control is off
cron_mode_refusal in dashboard/handlers/_shared.py a cron: key gets trust or trust_reads only: any other mode, a non-string one included, answers 403 mode_not_allowed, an unnamed slot answers 400 slot_required. The allowlist is the handler's own _SLOT_SCOPED_TRUST_MODES tuple, now defined here and imported by chat_handlers.py, so one constant names the slot-scoped modes
cron_creator_refusal, called from api_chat_mode (dashboard/chat_handlers.py) the creator fence from #16398, run on the resolved live slot: a slot another creator made answers 403 not_creator
_audit_cron_chat_denial in dashboard/handlers/_shared.py one SEL write for every cron refusal on the three routes; the two merged refusals use it too
audit_caller in api_chat_mode an admitted cron call is recorded as mode_change:<mode> under the cron's cron:<job id> key
and not cron_creator on the override revoke in api_chat_mode a cron's admitted trust or trust_reads never deactivates the global grant, declared in owner config or not, as the method's docstring promises; the owner's slot-scoped trust still ends a declared grant as before
mcp_cron.py cron_add description names ctx.set_session_mode() beside the open and seed methods

A cron sets one posture on one session it created, and nothing else. The method presents the same credential the four sibling methods present and calls the existing mode route, so there is one mode writer. The gateway holds a caller that presents an attested cron: key to three checks, in this order: the switch, the mode rule, the creator fence. The mode rule runs before the approval_modes governance read and before safety_override, so a cron's yolo is refused as a cron's whatever the policy says and nothing is armed or revoked. The fence runs on the slot the handler resolved, with no await between the resolution and the read, so it judges the slot object the grant is written to. A slot that is not live gets the handler's ordinary 400 unknown slot, because the mode route mints nothing.

An admitted call is the ordinary slot-scoped grant: trust or trust_reads is set on that slot and the session policy propagates as it does for the owner. The global grant is left alone whether it was armed ad hoc or declared in owner config: a scheduled run asking for auto-approval on its own session is not the operator selecting another mode, so the declared-grant exemption that applies to the owner does not reach a cron. Like the checks #16398 added on POST /api/chat/slots and POST /api/chat, these key on the cron: key the caller presents, so they are a courtesy for ScriptContext callers. The method sends the mode as given and keeps no allowlist of its own: a client-side refusal would leave no audit record, and the gateway is the one place the rule lives.

No in-tree caller other than ScriptContext presents a cron: key to the mode route, so no existing call changes. The audit keeps the shape #16398 used: chat.control denials naming the route, the slot and, for the mode rule, the mode. The three specs record the method, the rules and the pinning tests.

Backwards compatibility

Compatible: no existing in-tree caller presents a cron: key to POST /api/chat/mode, so no call that works today changes. Owner, dashboard and app-token requests are not judged by the three checks and keep every mode they have. ScriptContext's existing methods keep their signatures and results. The two merged refusals write the same audit fields through the shared helper.

Removes nothing: the diff adds one method, one helper, one shared audit write and two path entries; no route, key, field or function is removed or renamed.

Tests

  • test/test_cron_script_sessions.py: set_session_mode posts {slot, mode} to /api/chat/mode with the cron's credential and returns the receipt; a mode_not_allowed, not_creator or session_control_disabled refusal raises RuntimeError naming the code; the mode reaches the gateway as sent.
  • test/test_chat_routes_cron_switch.py: with the switch off a cron: key on POST /api/chat/mode gets 403 session_control_disabled and the denial is audited naming the path; with the switch on it is not refused; cron_mode_refusal admits trust and trust_reads, refuses yolo, normal, a blank, a different case, None, a number and a non-hashable value such as a list or a dict with an audited mode_not_allowed rather than a TypeError, is the facade's own _SLOT_SCOPED_TRUST_MODES tuple and not a second constant, still answers the 403 when the SEL write for the denial raises, refuses an unnamed slot with an audited slot_required, answers the mode before the missing slot, and judges nothing for a caller with no cron key.
  • test/test_chat_mode_cron.py, the real handler through a TestClient: a cron sets trust and trust_reads on its own slot and the record names its key; an unrelated slot is untouched; a slot-scoped cron trust leaves a live global grant alone, and a declared one too, while the owner's slot-scoped trust still ends a declared grant; a non-string mode such as a list is refused with the audited 403, never a crash; every other mode is refused with the posture, the policy and the override unchanged; a cron yolo never reaches governance; an absent mode is refused; an unnamed slot is refused; the owner's slot and another job's slot are refused with not_creator; a dead key gets unknown slot; the fence receives the resolved slot; the owner still sets every mode, on every slot at once and on a cron-created slot, and still arms yolo.
  • test/integration/test_script_cron_sessions.py, on a booted gateway: a real ScriptContext opens a session and sets trust then trust_reads on it, both on the SEL record under its key, with the override still off; yolo and normal each raise mode_not_allowed with the grant it held unchanged and the denial audited; a cron key is refused on the owner's slot, on another job's slot and with no slot named; with the switch off the route and the method answer session_control_disabled while the owner still sets the cron's slot; the owner sets and clears every mode on a cron-opened slot.
  • On main before the change, 37 of the new unit tests and 7 of the 8 new booted-gateway tests fail, and the nine added for the declared grant and the non-string mode fail against the first revision of this branch; the rest pin the owner path and the standing slot-scoped rule.

Manual verification

The sandboxed end-to-end run of a script cron did not run here, for the reason #16398 records: this host refuses unshare(CLONE_NEWUSER), so the cron sandbox cannot start. The booted-gateway tests present exactly the credential a sandboxed child holds, through a ScriptContext built from the runner's environment contract.

Related Issues

Closes #16653

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@hoang-phan98
hoang-phan98 requested a review from a team as a code owner October 4, 2026 06:13
@hoang-phan98
hoang-phan98 requested a review from buluoray October 4, 2026 06:13
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 4, 2026
@github-actions

github-actions Bot commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of d413298559778a4cba0906275dbda84986fd8cdd — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Before merge, confirm that a cron's admitted trust still goes through the approval_modes governance read and is not short-circuited by it.

[DESIGN-REVIEWED] d413298

Description read

[DESCRIPTION-READ] 10da7cbe801302f083f0d351e01083493a66c1218ddfb666cd24607805b18200

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of d413298559778a4cba0906275dbda84986fd8cdd — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

First-Principles-Verdict: PASS

Check one thing before merge: a cron's trust on a Slack-linked slot now skips the persisted channel trust, and the description never mentions that.

Not justified as shipped

  • Item 7 — undeclared: the and not cron_creator checks on mgr._channels[linked_ch].trusted = True and _trusted_chs are not in the description's table. The change keeps a cron from writing persisted Slack channel trust, so it removes surface rather than adding it, but it is still undeclared.

What this change ships

Inventory (10 items) — 9 justified

Intent: let an unattended script cron give the session it opened trust or trust_reads, so the session does not stall on its first tool prompt. ADDITION.

  1. Script crons can call ctx.set_session_mode(slot, mode) on a session they opened — justified
  2. With agent.session_control off, a cron calling the mode route gets 403 session_control_disabled — justified
  3. A cron can set only trust or trust_reads; yolo, normal and non-strings get 403 mode_not_allowed — justified
  4. A cron that names no slot gets 400 slot_required instead of changing every slot — justified
  5. A cron changing the mode of a slot it did not create gets 403 not_creator — justified
  6. The audit log records a cron's mode change under its own cron:<job id> key — justified
  7. A cron's trust on a Slack-linked slot no longer marks that channel trusted — undeclared
  8. A cron's slot-scoped trust never revokes the global or declared YOLO grant — justified
  9. All three cron refusals share one audit write; _SLOT_SCOPED_TRUST_MODES moved to one shared definition — justified
  10. The cron_add tool description now names ctx.set_session_mode() — justified

[FIRST-PRINCIPLES-REVIEWED] d413298

Description read

[DESCRIPTION-READ] de007c99492db98c1bf1b29712dacd5c74c9efa118c5152472d34dc2b86e72e7

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed d413298559778a4cba0906275dbda84986fd8cdd — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] d413298

Verdict parsed from the review's SHA-scoped output markers for commit d413298559778a4cba0906275dbda84986fd8cdd.

False positive or not applicable? A repository writer can comment:
/ai-review override fable d413298559778a4cba0906275dbda84986fd8cdd: <one-sentence reason>

@hoang-phan98

hoang-phan98 commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor Author

CI note on head 700ae28: Backend Tests (Windows) (1) is red for three tests and Backend Tests (3.12, 1) for two, none from this diff.

The two shared ones are inherited from main. test/test_chat_handlers_composition_contract.py::test_every_name_the_handlers_bound_at_the_base_still_resolves and ::test_a_fresh_interpreter_sees_every_base_public_name fail with ['re']: #15917 (7279426) removed import re from src/kiro_crew/dashboard/chat_handlers.py while the test's _BASE_NAMES still lists re. Both fail the same way on origin/main at efd0181de without this branch. This PR touches neither that import nor that test, so the fix belongs on main.

The third Windows failure, test/test_spawn_approval_crew_log.py::test_a_cancelled_wait_still_answers_its_own_request, is a Windows file-lock failure. It passes on main locally and this PR does not touch that code. I will re-run the shard once when the run completes.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 4, 2026
@hoang-phan98
hoang-phan98 force-pushed the feat/cron-set-session-mode-16653 branch from 700ae28 to e8f7d52 Compare October 4, 2026 06:45
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 4, 2026
@github-actions

github-actions Bot commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of d413298559778a4cba0906275dbda84986fd8cdd and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] d413298

False positive or not applicable? A repository writer can comment:
/ai-review override gpt d413298559778a4cba0906275dbda84986fd8cdd: <one-sentence reason>

@hoang-phan98

Copy link
Copy Markdown
Contributor Author

self-added: yes
mechanism: _SLOT_SCOPED_TRUST_MODES now lives in dashboard/handlers/_shared.py and chat_handlers.py imports it; _CRON_SESSION_MODES is gone.

  • span=d1335e0c4b04 — duplicate of _SLOT_SCOPED_TRUST_MODES

Outcome: fixed in e8f7d52.
Rationale: the frozenset copy is deleted. The one tuple is defined in handlers/_shared.py, where cron_mode_refusal reads it as the cron allowlist, and chat_handlers.py imports the same object for the slot-scoped grant check, so the facade name still resolves. Because it is a tuple, a non-string mode such as a list answers the audited 403 mode_not_allowed instead of raising. Pinned by test_a_non_hashable_mode_is_refused_rather_than_raised and test_the_allowlist_is_the_handlers_slot_scoped_tuple in test/test_chat_routes_cron_switch.py, and by test_a_cron_sending_a_non_string_mode_is_refused_not_crashed against the real handler in test/test_chat_mode_cron.py; all failed before the fix.

@hoang-phan98

Copy link
Copy Markdown
Contributor Author

mechanism: and not cron_creator on the override-revoke condition in api_chat_mode, the same exemption an app token already has.

  • span=d085816e0bea — src/kiro_crew/dashboard/chat_handlers.py:9109 declared grant ended by a cron trust

Outcome: fixed in e8f7d52.
Rationale: a caller presenting a cron: key is now excluded from the revoke, so its admitted trust or trust_reads never runs deactivate, whether the global grant was armed ad hoc or declared in owner config. That matches the docstring promise. The owner path is unchanged: the owner's slot-scoped trust still ends a declared grant. Pinned in test/test_chat_mode_cron.py by test_a_cron_slot_scoped_trust_leaves_a_declared_global_grant_alone for both modes, which failed before the fix, and by test_the_owner_slot_scoped_trust_still_ends_a_declared_global_grant as the contrast. The spec sentences in security.md and learn-cron-dashboard.md record the rule.

@hoang-phan98

Copy link
Copy Markdown
Contributor Author

Rebased: 700ae2838 onto main at efd0181de, now e8f7d5247, still one commit. Scoped re-run on the new head: 1987 unit tests across the mode-route, cron-gate, cron-script and overlap files pass, the booted-gateway script-cron suite passes (25), flake8, mypy and docs-lint pass. The only local reds are the two _BASE_NAMES ['re'] composition-contract tests that main carries, recorded above. This push also carries the two review fixes recorded in the disposition comments.

@hoang-phan98

hoang-phan98 commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor Author

CI note on head e8f7d52: five checks are red, all for the two failures main carries, none from this diff.

Backend Tests (3.12, 3) and Backend Tests (Windows) (3): test/test_review_repair_routing_skill.py::test_slim_skills_do_not_regrow_duplicate_guidance_or_wire_model_ids[prepare-pr-68000] fails with 68077 <= 68000. Main commit efd0181de (#16196) grew src/kiro_crew/builtin_skills/kirocrew-dev/prepare-pr/SKILL.md from 66306 to 68077 bytes, past the test's 68000-byte ceiling. The test fails the same way on origin/main at efd0181de without this branch, and this PR touches neither the skill file nor the test.

Backend Tests (3.12, 1) and Backend Tests (Windows) (1): only the two _BASE_NAMES ['re'] composition-contract tests from the note above, inherited from 727942627 (#15917). The Windows file-lock failure from the previous head did not recur, so no re-run is needed.

Coverage Gate: fails closed on backend-test=failure, which is the aggregate of the four shards above. No coverage threshold was evaluated.

@hoang-phan98
hoang-phan98 force-pushed the feat/cron-set-session-mode-16653 branch from e8f7d52 to 1aaa404 Compare October 4, 2026 07:24
@hoang-phan98

Copy link
Copy Markdown
Contributor Author

mechanism: wording only, in the api_chat_mode docstring and the commit message; no audit code changed.

  • span=27afc892be32 — src/kiro_crew/dashboard/chat_handlers.py:9000 docstring overclaimed the refusal audit

Outcome: fixed in 1aaa404.
Rationale: the docstring and the commit message now say what the audit records. An admitted call is recorded as mode_change:<mode> under the cron's own key. Each refusal is recorded by _audit_cron_chat_denial as a chat.control denial attributed to internal, naming the route, the slot and the mode, the shape every cron-gate refusal on the chat routes already shares. The spec text and the PR body already described the records this way; only the two sentences changed. A new gate-level test also pins that a refusal still answers 403 when the SEL write for the denial raises.

@hoang-phan98

Copy link
Copy Markdown
Contributor Author

Rebased: e8f7d5247 onto main at 2f8c9a783, now 1aaa404e9, still one commit. This push carries the wording fix recorded in the disposition above and one added test for the denial-audit fallback. Scoped re-run on the new head: 1530 unit tests across the mode-route, cron-gate and cron-script files plus test/test_loop_watchdog.py pass, flake8, mypy and docs-lint pass. The only local reds are the two _BASE_NAMES ['re'] composition-contract tests, which main at 2f8c9a783 still carries along with the prepare-pr size test.

@hoang-phan98
hoang-phan98 force-pushed the feat/cron-set-session-mode-16653 branch from 1aaa404 to 1b4e094 Compare October 4, 2026 07:46
@hoang-phan98

Copy link
Copy Markdown
Contributor Author

Rebased: 1aaa404e9 onto main at 8b7991d48, now 1b4e094d9, still one commit with identical added and removed lines. The two new main commits touch src/kiro_crew/cron_script.py and docs/system-specs/modules/learn-cron-dashboard.md in places this PR does not, and the rebase applied cleanly. Scoped re-run on the new head: the mode-route, cron-gate, cron-script and composition-contract files pass, 10047 tests. main at a09427ef2 (#16695) dropped re from the composition-contract name pin, so the two ['re'] failures from the earlier notes are gone on this head. The prepare-pr size test still fails on origin/main at 8b7991d48 and remains the one inherited failure.

@hoang-phan98

Copy link
Copy Markdown
Contributor Author
  • span=15cd2996ec2b

Outcome: accepted as shipped, by the maintainer's ruling, the same position #16398 recorded for open_session and send_to_session; no code change.

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 4, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor

Reviewed, not approving from my side: this lets a script cron set trust or trust_reads (auto-approve tools) on a session it opened, via POST /api/chat/mode. The scoping looks careful (one slot the cron created, yolo and normal refused, cron_mode_refusal), but granting auto-approval from an unattended job is a permission decision, and #16653 is still needs-human. That needs a maintainer and a security owner's sign-off. CI is green.

@hoang-phan98
hoang-phan98 added this pull request to stack #16909 October 5, 2026 05:57
@hoang-phan98
hoang-phan98 force-pushed the feat/cron-set-session-mode-16653 branch from 1b4e094 to 605475f Compare October 5, 2026 07:32
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 5, 2026
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 5, 2026
@hoang-phan98
hoang-phan98 force-pushed the feat/cron-set-session-mode-16653 branch from 605475f to 005fe2b Compare October 5, 2026 08:08
@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 5, 2026
@hoang-phan98
hoang-phan98 force-pushed the feat/cron-set-session-mode-16653 branch from 005fe2b to 4eded49 Compare October 5, 2026 08:59
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: passed Eligible automated validation passed for the current revision labels Oct 5, 2026
A script cron that opens and seeds its own session could not set that
session's approval mode, so unattended work in it waited on each tool
prompt. set_session_mode(slot, mode) posts the slot and mode to the
mode route with the cron's own credential, and the gateway holds a
caller that presents an attested cron: key to one rule set: trust or
trust_reads only, on one named slot that same cron created, refused
while agent.session_control is off. An admitted call is recorded under
the cron's key; each refusal is recorded as a chat.control denial
attributed to internal, naming the route, slot and mode. Owner and
app callers are unchanged.

The allowlist is the handler's own slot-scoped tuple, moved where both
readers import it, so a non-string mode is refused rather than raised.
A cron's admitted trust never deactivates the global grant, declared
or not, which is what the method promises.

Closes #16653
@hoang-phan98
hoang-phan98 force-pushed the feat/cron-set-session-mode-16653 branch from 4eded49 to d413298 Compare October 5, 2026 09:16
@hoang-phan98

Copy link
Copy Markdown
Contributor Author
  • span=a7e1ff0be717

Outcome: fixed in d413298. Rationale: the slot-scoped mode change no longer modifies or reports the linked channel, and the regression test failed before the fix and passes now.

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 5, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor

Re-reviewed at d413298. The new commit keeps cron-set trust from marking the linked Slack channel as trusted, and a regression test covers it. That's a good fix. My hold is still in place, though: a script cron can still turn on auto-approve (trust/trust_reads) for a session it opened. #16653 is still needs-human, and I haven't seen a maintainer or security owner accept that an unattended job may grant auto-approval. Once that sign-off is on #16653 or here, I'm happy to approve. CI and scoping look fine.

@bolichen97 bolichen97 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed on behalf of the maintainers (sweep 2026-10-06): full diff read, callers verified against current main, readiness passed, required checks green, no blocking review threads. Policy sign-off on the owner's behalf (#16653): a script cron may set trust/trust_reads on the one dashboard session it created. Main already let an internal-credential cron post ANY mode to /api/chat/mode unfenced, so this merge narrows the gateway (yolo/normal, foreign slots and switch-off are now refused and SEL-audited) while documenting the one supported shape. A cron script is operator-authored code running as the operator, so no privilege is gained that the operator did not already hold. Approving and merging.

@bolichen97
bolichen97 merged commit 9ad36de into main Oct 6, 2026
98 checks passed
@bolichen97
bolichen97 deleted the feat/cron-set-session-mode-16653 branch October 6, 2026 07:06
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(cron): add ScriptContext.set_session_mode for cron sessions

3 participants