CoCo, or the application, needs something only the user knows. The question is answered inside its block; nothing leaves before Send answer. The field below keeps queuing the next message.
38 · Question choose, then send; Skip lets CoCo go on without
CoCo
Draft reminders for late timesheets
Read 9 files, completed
Read
98_project/timesheets/*.md
Result
9 files
Which week should the reminders cover?
39 · Question, an answer chosen a queued message waits behind it
CoCo
Draft reminders for late timesheets
Read 9 files, completed
Read
98_project/timesheets/*.md
Result
9 files
Which week should the reminders cover?
Then list the open risksQueued
40 · Question, something else the user's own words, inside the block
CoCo
Draft reminders for late timesheets
Which week should the reminders cover?
41 · Question, several may apply boxes instead of one choice
CoCo
Draft reminders for late timesheets
Who should receive them?
42 · Several questions one at a time; all sent together at the end
CoCo
Draft reminders for late timesheets
Question 2 of 3
Who should receive them?
43 · A form, long scrolls inside; the buttons stay; Send waits for Next steps
CoCo
Prepare this week's status report
What should this week's report say?
44 · Answered question and answer read as the conversation
CoCo
Draft reminders for late timesheets
Read 9 files, completed
Read
98_project/timesheets/*.md
Result
9 files
Which week should the reminders cover?
This week
Read 4 files, running
Read
98_project/timesheets/*.md
45 · Skipped said once, on the question; CoCo goes on
CoCo
Draft reminders for late timesheets
Read 9 files, completed
Read
98_project/timesheets/*.md
Result
9 files
Which week should the reminders cover?Skipped
I will cover this week, the one still open.
46 · Question, minimised the pill says it is a question
lormeau-regulatory-reportingPhase 3 · functional_spec.md has blocking tags
saint-aubry-patient-flowPhase 2 · workstreams WS2 and WS3 are not Done
A plan to approve
CoCo says what it intends to do and waits. Approving a plan is not a standing permission: each command and each change still asks.
47 · Planning only the mode is said once, under the header
CoCo
Planning only. Nothing is changed yet.
Prepare this week's report and fix what the audit found
Read 4 files, running
Read
98_project/weeklies/*.md
48 · Plan presented approve it or decline it; what approving does
CoCo
Prepare this week's report and fix what the audit found
Go ahead with this plan?
Read last week's report and this week's timesheets.
Run the project audit.
Write the report of week 41 from last week's structure.
Correct the two specifications the audit flags.
If you approve, CoCo starts. It still asks before each command or change.
49 · Plan, long twelve steps scroll inside; the buttons stay
CoCo
Prepare this week's report and fix what the audit found
Go ahead with this plan?
Read last week's report.
Read this week's timesheets, 9 people.
Read the open risks and actions.
Run the project audit.
List what the audit reports, worst first.
Write the report of week 41 from last week's structure.
Fill the progress section from the timesheets.
Fill the risks section from the register.
Correct the functional specification where the audit flags it.
Correct the data contract where the audit flags it.
Run the audit again.
Summarise what changed, file by file.
If you approve, CoCo starts. It still asks before each command or change.
50 · Decline pressed a reason is offered, never required
CoCo
Prepare this week's report and fix what the audit found
Go ahead with this plan?
Read last week's report and this week's timesheets.
Run the project audit.
Write the report of week 41 from last week's structure.
Correct the two specifications the audit flags.
51 · Plan approved the plan folds to one line; work starts
CoCo
Prepare this week's report and fix what the audit found
The plan you approved, completed
Read last week's report and this week's timesheets.
Run the project audit.
Write the report of week 41 from last week's structure.
Correct the two specifications the audit flags.
Read last week's report, running
Read
98_project/weeklies/20261002_weekly.md
52 · Plan declined, with a change the reason is the user's message
CoCo
Planning only. Nothing is changed yet.
Prepare this week's report and fix what the audit found
The plan CoCo proposed, not runDeclined
Read last week's report and this week's timesheets.
Run the project audit.
Write the report of week 41 from last week's structure.
Correct the two specifications the audit flags.
Only the report. Leave the specifications alone.
53 · Plan, minimised the pill says it is a plan
lormeau-regulatory-reportingPhase 3 · functional_spec.md has blocking tags
saint-aubry-patient-flowPhase 2 · workstreams WS2 and WS3 are not Done
54 · A plan written as an answer planning only: the strip carries the way out
CoCo
Planning only. Nothing is changed yet.
Prepare this week's report and fix what the audit found
I would read last week's report and the timesheets, run the audit, write the report of week 41, then correct the two specifications the audit flags.
55 · Two things wait one at a time, in the order they came; the next is named
CoCo
What is the git status of my repository?
First of 2 waiting for you. Next: a question.
Allow CoCo to look at what has changed in your project files?
ReadsThe files of marenval-fleet-telemetry
Show commandHide command
git status
A standing permission
Offered only when the application sends one with the request; the Cockpit sends none, and frame 19 is then the whole request. It names what it covers, ends with the conversation, and is taken back from the menu.
56 · Request, with the choice one more line; Allow still means once
CoCo
What is the git status of my repository?
Allow CoCo to look at what has changed in your project files?
ReadsThe files of marenval-fleet-telemetry
Show commandHide command
git status
57 · The choice ticked what it covers and until when; the button says so
CoCo
What is the git status of my repository?
Allow CoCo to look at what has changed in your project files?
ReadsThe files of marenval-fleet-telemetry
Show commandHide command
git status
CoversLooking at what has changed in the files of marenval-fleet-telemetryUntilThis conversation ends, or you take it back in the menu
58 · Granted said once, with the way back
CoCo
What is the git status of my repository?
CoCo no longer asks before it looks at what has changed in these files.
Look at what has changed in your project files, running
bash
git status
Allowed by you
59 · Later, not asked the step says why, in its detail
CoCo
And now, anything new?
Look at what has changed in your project files, completed
bash
git status
Result
On branch feat/cockpit
nothing to commit, working tree clean
Not asked: you allowed it for this conversation
Nothing has changed since this morning.
60 · Menu, everything switched on every line below the first two is optional
CoCo
Prepare this week's status report
Overall progress. Phase 6 of 7, 2 of 4 modules generated, 58 days remaining. Budget verdict Green. Risks and blockers.M3 is 6 days late; R-001 is open; no meeting logged for 36 days. Next steps. Camille Aubert logs the weekly meeting and moves M3 with a reason.
61 · Without asking what was given, and one button to take each back
CoCo
Prepare this week's status report
Overall progress. Phase 6 of 7, 2 of 4 modules generated, 58 days remaining. Budget verdict Green. Risks and blockers.M3 is 6 days late; R-001 is open; no meeting logged for 36 days. Next steps. Camille Aubert logs the weekly meeting and moves M3 with a reason.
CoCo no longer asks before it:
Looks at what has changed in the files of marenval-fleet-telemetry