core/agent
8
0
Fork 0
Code Issues 5 Pull requests Projects Releases Packages Wiki Activity Actions

docs(fleet): document fleet task ≠ AgentSession separation

Browse source 
Fleet tasks deliberately do not create AgentSession records.
AgentSession's work_log / artefacts / handoff / replay semantics are
designed for interactive, replayable, handoff-capable work — fleet
tasks are atomic assign→complete events with no in-between state
to replay. If a fleet-task handler needs session semantics, it
should start its own AgentSession via AgentSessionService when the
work begins.

Closes tasks.lthn.sh/view.php?id=94

Co-authored-by: Codex <noreply@openai.com>
Co-Authored-By: Virgil <virgil@lethean.io>
This commit is contained in:
Snider 2026-04-23 18:16:22 +01:00
parent 2a8b847e29
commit 1095795b1c
3 changed files with 18 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/php-agent/RFC.md
View file

@ -273,6 +273,10 @@ WorkspaceState::set($planId, 'discovered_pattern', 'observer');
$pattern = WorkspaceState::get($planId, 'discovered_pattern');
```
### 7.x Fleet tasks vs sessions
Fleet tasks (AssignTask / CompleteTask) are deliberately out-of-session. AgentSession's work_log, artefacts, handoff, and replay semantics are designed for interactive / MCP-driven flows, not for the atomic assign→complete shape of fleet distribution. If a fleet task's handler needs session-style replay, that handler should start its own AgentSession via AgentSessionService when it begins the work.
---
## 8. API Key Security

7
php/Actions/Fleet/AssignTask.php
View file

@ -8,6 +8,13 @@ use Core\Actions\Action;
use Core\Mod\Agentic\Models\FleetNode;
use Core\Mod\Agentic\Models\FleetTask;
/**
* Fleet tasks intentionally do not create AgentSession records. AgentSession tracks interactive,
* replayable, handoff-capable work with a work_log and artefact history; fleet tasks are atomic
* assign→complete events with no in-between state to replay. If a fleet task's work requires
* session semantics, the agent executing the task should start an AgentSession itself via
* AgentSessionService.
*/
class AssignTask
{
use Action;

7
php/Actions/Fleet/CompleteTask.php
View file

@ -9,6 +9,13 @@ use Core\Mod\Agentic\Actions\Credits\AwardCredits;
use Core\Mod\Agentic\Models\FleetNode;
use Core\Mod\Agentic\Models\FleetTask;
/**
* Fleet tasks intentionally do not create AgentSession records. AgentSession tracks interactive,
* replayable, handoff-capable work with a work_log and artefact history; fleet tasks are atomic
* assign→complete events with no in-between state to replay. If a fleet task's work requires
* session semantics, the agent executing the task should start an AgentSession itself via
* AgentSessionService.
*/
class CompleteTask
{
use Action;