Business Performance Consulting Sdn Bhd User Guides
02

Daily Workflow

Odoo 19 Enterprise · BPC Session

A typical work block: open a session, work in Odoo, close the session. Same three steps whether I am on MacBook or Studio.

Process lifecycle

Open Work in Odoo Close
1

Start of session

Run session open at the start of any work block, especially when switching between MacBook and Studio. It does three things in order: git pull to collect any changes the other machine pushed, read the last CLOSE line from the session log so I see when and from where the previous block ended, then pull my current open To-do tasks from Odoo into exports/latest.json. Output confirms everything with a task count.

2

Work in Odoo

I work directly in the Odoo To-do app in my browser — drag tasks between stages (Inbox, Today, This Week, Next Week, Later, Done), tick them complete, add new ones as they come up. No terminal commands are needed during the work itself. The session CLI is only for bookending: open at start, close at end.

3

End of session

Run session close before switching machines, closing the laptop for a break, or ending the day. It pulls the final Odoo state into latest.json to capture everything I just did, writes a CLOSE line to the session log, then commits and pushes the repo to GitHub. After this, the other machine can pick up cleanly.

4

Switching machines

Say I worked on Studio in the morning and want to continue on MacBook after lunch. On Studio I run session close. On MacBook I run session open. That is the whole handover. The second open pulls down everything Studio pushed plus a fresh snapshot from Odoo. If I made changes in Odoo on my phone during lunch, those are in the snapshot too because the open command always pulls fresh from Odoo.

5

If I forget to close

Nothing breaks. Next time I run session open anywhere, it still pulls the latest Odoo state and still git pulls any outstanding changes. The only downside is the session log missing a clean CLOSE line, which is cosmetic. Claude still sees the latest data.

Commit discipline The commit-on-close pattern means GitHub accumulates one commit per session. Over weeks this builds a useful audit trail of when I worked on what. Do not be tempted to manually commit inside the repo — let session close handle it so the log stays clean.