Copy Buttons

Copy button templates follow a layered configuration model. Server defaults provide baseline templates, project-level overrides customize for team workflows, and task-specific configurations handle one-off scenarios.

Templates use double-brace placeholders that are resolved against the active plan and session context at click time. The resolution engine supports nested context access and conditional sections.

// Example template with placeholders
You are an AI coding assistant. Execute the following plan:

{{IMPLEMENTATION_PLAN}}

Working on task: {{TASK_DESCRIPTION}}

Selected files for context:
{{SELECTED_FILES}}

Model: {{MODEL_NAME}}
Session: {{SESSION_ID}}

Resolution order: Job metadata first, then plan content, then session context. Undefined placeholders are preserved in the output for debugging.

When a button is clicked, the template processor executes a multi-step pipeline: placeholder extraction, context lookup, value substitution, and output formatting.

Buttons configured for terminal handoff write directly to the PTY session input buffer. The resolved template appears as if typed by the user, triggering agent execution immediately.

// Terminal handoff implementation
async fn handoff_to_terminal(
    session_id: &str,
    content: &str,
    template_id: &str,
) -> Result<HandoffResult> {
    // Get PTY writer for session
    let writer = terminal_manager.get_writer(session_id)?;

    // Write content to PTY input buffer
    writer.write_all(content.as_bytes()).await?;

    // Log the action for audit
    copy_button_actions.insert(CopyButtonAction {
        session_id: session_id.to_string(),
        template_id: template_id.to_string(),
        content_hash: sha256(content),
        created_at: Utc::now(),
    })?;

    Ok(HandoffResult::Terminal { session_id })
}

Buttons configured for clipboard copy the resolved template to the system clipboard using the Tauri clipboard API. This enables handoff to external tools like IDE terminals or web-based agents.

Every copy button action is linked to job metadata for complete traceability. The audit record includes the source plan, target session, resolved content hash, and user context.

-- copy_button_actions table schema
CREATE TABLE copy_button_actions (
    action_id    TEXT PRIMARY KEY,
    plan_id      TEXT NOT NULL REFERENCES implementation_plans(id),
    job_id       TEXT REFERENCES background_jobs(id),
    session_id   TEXT REFERENCES terminal_sessions(session_id),
    template_id  TEXT NOT NULL,
    content_hash TEXT NOT NULL,  -- SHA-256 for integrity verification
    created_at   TEXT NOT NULL
);

-- Query to trace plan handoffs
SELECT * FROM copy_button_actions
WHERE plan_id = ?
ORDER BY created_at DESC;

Retention: Audit records are retained for 90 days by default, configurable in project settings.

PlanToCode ships with several default copy buttons that cover common workflows. These can be customized or extended through project settings.

Copy buttons can be customized at multiple levels: global defaults, project-level overrides, and per-task configurations.

The copy button editor in Settings allows drag-and-drop reordering, inline label editing, and template content modification. Changes are debounced and persisted automatically.

Copy buttons appear in plan viewers and terminal headers. Each button shows a preview popover with the resolved content and token estimate before execution.

Copy buttons work across desktop and mobile clients with consistent behavior. The iOS client uses the same placeholder resolution logic and can send content to linked terminals.