You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prompt is re-sent on resume. In build_auggie_args(), --instruction "$PROMPT" is always appended when a task prompt is set, regardless of whether --continue is also being passed. According to upstream docs, when both are passed "new instructions are appended to the resumed session" -- meaning the same task prompt gets re-sent as a new message in the resumed conversation.
--type is missing. The agentapi server command in start_agentapi_server() doesn't pass --type auggie.
To reproduce: set continue_previous_conversation = true, report_tasks = true, and an ai_prompt. Start the module, have a conversation, stop, restart. --instruction will be present alongside --continue, and --type will be absent from the agentapi process args.
Desired outcome
continue_previous_conversation defaults to true.
report_tasks defaults to true.
The task prompt is only sent on cold start, not when resuming.
--type auggie is passed to agentapi server.
Expose enable_state_persistence in main.tf (default true) and pass it through to the module "agentapi" block so the Coder UI preserves chat history across restarts, matching the agent's resumed session.
Risks
Headless --continue is unverified. It's unknown whether auggie's --continue works correctly when wrapped by agentapi's PTY. This needs to be tested in a workspace before shipping. If it doesn't work, keep the default at false and document the limitation.
--continue with no prior session is unverified. Unlike OpenCode (which gracefully creates a new session), auggie's behavior when --continue is passed on first run with no existing sessions is unknown. Test this.
Backend dependency unknown. Auggie's session data may be partially stored on Augment's cloud servers. If --continue requires network connectivity, air-gapped environments can't use it.
Problem
Four issues:
Resume is off by default. The module passes
--continueto auggie whencontinue_previous_conversationis true, but this variable defaults tofalse.Task reporting is off by default.
report_tasksdefaults tofalse, so Auggie tasks don't benefit from activity-based TTL. This may be related to Bug: Auggie module is not reporting in task mode in latest versions #614.Prompt is re-sent on resume. In
build_auggie_args(),--instruction "$PROMPT"is always appended when a task prompt is set, regardless of whether--continueis also being passed. According to upstream docs, when both are passed "new instructions are appended to the resumed session" -- meaning the same task prompt gets re-sent as a new message in the resumed conversation.--typeis missing. Theagentapi servercommand instart_agentapi_server()doesn't pass--type auggie.To reproduce: set
continue_previous_conversation = true,report_tasks = true, and anai_prompt. Start the module, have a conversation, stop, restart.--instructionwill be present alongside--continue, and--typewill be absent from the agentapi process args.Desired outcome
continue_previous_conversationdefaults totrue.report_tasksdefaults totrue.--type auggieis passed toagentapi server.enable_state_persistenceinmain.tf(defaulttrue) and pass it through to themodule "agentapi"block so the Coder UI preserves chat history across restarts, matching the agent's resumed session.Risks
--continueis unverified. It's unknown whether auggie's--continueworks correctly when wrapped by agentapi's PTY. This needs to be tested in a workspace before shipping. If it doesn't work, keep the default atfalseand document the limitation.--continuewith no prior session is unverified. Unlike OpenCode (which gracefully creates a new session), auggie's behavior when--continueis passed on first run with no existing sessions is unknown. Test this.--continuerequires network connectivity, air-gapped environments can't use it.Version bump
minorRefs #614, #696, coder/internal#1258