argus-agent replay
Since next
Play a recorded assistant session again against a project: the same engine calls that landed a change, as an agent of the same name, with its recorded narration printed as stream-json at its recorded times (crate::replay).
Usage
argus-agent replay [OPTIONS] <TRANSCRIPT>Arguments
| Argument | Description |
|---|---|
<TRANSCRIPT> | The Ask AI box's transcript (.argus/editor/assistant/<run>.jsonl) or a client's stream-json |
Options
| Flag | Value | Default | Allowed values | Description |
|---|---|---|---|---|
--project | <PROJECT> | The project folder to replay into. The current folder when absent | ||
--agent | <AGENT> | Assistant | The agent's name on the roster and in the journal | |
--speed | <SPEED> | 1 | How much faster than recorded (2 is twice as fast) | |
--max-gap-ms | <MAX_GAP_MS> | 4000 | The longest recorded wait kept, in milliseconds, before speed applies | |
--rewrite | <REWRITE> | RECORDED=HERE: a folder the recorded calls name (a checkout a file was imported from), as it is on this machine. Repeatable. The recorded project folder is rewritten without it | ||
--tool-names | <TOOL_NAMES> | dotted | How tools/list spells the names. dotted is the interface's own (scene.read); underscore is for a client that namespaces a tool into an identifier and will not take a dot (scene__read); hyphen for one that also takes no __ inside a tool's name (Grok: scene-read). tools/call takes any spelling whichever this is | |
--toolsets | <TOOLSETS> | "" | Toolsets to list from the start, beyond the core: comma-separated names, or all. For a client that does not refetch tools/list when told it changed; one that does can call tools.enable instead and pay for the tools only when it needs them. ARGUS_AGENT_TOOLSETS when absent, so a harness can set it for every server it starts |
Example
argus-agent replay <TRANSCRIPT>