diff --git a/doc/onboarding-chat.md b/doc/onboarding-chat.md index 6954e5d85d7..deaf5e791b7 100644 --- a/doc/onboarding-chat.md +++ b/doc/onboarding-chat.md @@ -26,6 +26,7 @@ request can create work directly. Project selection, budgets and hiring gates retain their normal authority. The conversation remains available after handoff. Local subscription setup waits for verified sign-in before enabling Connect. -Pasting a Claude authorization code submits it automatically and shows a finishing state; a rejected code -offers a fresh sign-in immediately. Switching providers clears the previous -provider's model so subscription verification uses a compatible model. +Pasting a Claude authorization code submits it automatically and shows a finishing +state; a rejected code offers a fresh sign-in immediately. Switching providers +clears the previous provider's model so subscription verification uses a +compatible model. diff --git a/server/src/services/onboarding-chat-prompt.ts b/server/src/services/onboarding-chat-prompt.ts index e6feb865712..7dee0c0dc2e 100644 --- a/server/src/services/onboarding-chat-prompt.ts +++ b/server/src/services/onboarding-chat-prompt.ts @@ -7,4 +7,3 @@ Let the user choose an interview or ordinary conversation. Offer to interview th Once the goal and exit criteria are clear, suggest a concrete task for the user to accept. Use request_human_input with interactionKind: "suggest_tasks", a stable idempotencyKey and payload.tasks containing a clientKey, concise title, self-contained description with context, constraints and acceptance criteria, initialPlan and assigneeAgentId defaulting to yourself. With HTTP, POST the equivalent suggest_tasks interaction to /api/issues/{issueId}/interactions. A suggestion is not an execution task; acceptance creates the task atomically, so read result.createdTasks and link that task rather than creating it again. Reuse a suitable existing projectId when available. If no suitable project exists, omit projectId from the suggestion; do not create a project just to prepare a proposal. After acceptance, use the normal project controls if the approved work needs a new project. Do not create a task, project or hire agents just because onboarding finished, the user described an idea or answered questions. Create execution work only after the user accepts a proposal or explicitly asks you to create a task. An explicit task-creation request authorizes creating it directly once material scope questions are answered; do not ask them to approve the same scope again. Use the normal project and task handoff controls, preserve hiring and budget gates, and link the resulting task in this conversation. Keep this chat available for further discussion.`; export const ONBOARDING_CHAT_GREETING_DIRECTIVE = `The user has just arrived in this visible chat after onboarding. Greet them now with a short, warm message in your own voice using the onboarding context. You can start with "Welcome to Paperclip! I'm , your first agent teammate." Invite them to tell you what they want to achieve, or ask you to interview them to work it out together. If they already supplied a goal, acknowledge it and ask the next useful question instead of asking them to repeat it. Do not create tasks, projects, hires, plans or question cards during this greeting. Send the welcome as your conversational reply so it streams to the user. If a user message is already present, answer it naturally instead of repeating an opening greeting.`; -