The details, dated
Journal
67 working sessions with Claude, ChatGPT and Codex: decisions, design, development and lessons learned. Each entry identifies the AI used. Search or filter by tag below.
From news watch to media: what we built with ChatGPT
Short and long podcasts, Sunday comics, iAstro and design: how our news watch is evolving, with a method that can be adapted to other subjects.
-
A central “Brain” so we stop handing out the server keys to everyone
To create a product in Odoo through an agent, you used to need an SSH key on the server — so either Hugo did everything, or broad, untraceable access got handed out. A central service (the “Brain”) now holds the secrets server-side and exposes business capabilities behind a token → an identity → a role (read / prepare / write / publish), logging who did what. Two surfaces (a command-line skill + a protected internal web page), guardrails carried over from the legacy tool (anti-duplicate reconciliation before any creation, never auto-published), 3 accesses distributed: two people add and deploy their own capabilities without going back through Hugo.
Growth: replacing ten dashboards with an action queue
Loose ideas at the end of the week, a weekend with ChatGPT and Codex, then Growth running in production by Tuesday. Data, BigQuery, the application and a reusable agentic core were built to turn facts into approved actions.
-
AI doesn't code my request — it verifies what it assumes
Odoo change requests used to arrive as a one-liner — no where, no what-on-click, no « what must not move ». An internal chain frames them: a guided form (8 fields, dictation possible), screenshot and auto-transcribed-video upload, then a two-pass AI review — it asks structured questions, the server checks them in the real Odoo database read-only, the AI concludes. It reclassified a dev request as ten minutes of configuration, and saw that a solution didn't remove the supplier calls it claimed to avoid. ~100 s and a few cents per review.
-
HiFi watch: the daily bot repaired, expanded (30 → 64 sources) and hardened
The daily HiFi watch bot (Telegram) had been down since June 15 — the hard-coded AI model had reached end of life. Repaired (model now auto-selected, the watch can no longer break on an update), heavily expanded (30 → 64 sources: French specialist and mainstream press, Europe, Reddit, Head-Fi/diyAudio forums, YouTube) and hardened (HTML delivery, deduplication, alert if a source dies for 3 days, ~1-month memory, capped cost ~€3-4/month). Validated in production: 125 articles → 123 topics → 4 Telegram messages, error-free.
-
Price tracking & automatic competitive alignment
We couldn't manually watch hundreds of references against Darty, Boulanger, Fnac or Son-Vidéo. A rules engine in Odoo (cobra_price_rules) reads competitor prices delivered by Wiser several times a day and computes a target price — best valid competitor, bounded by a minimum margin. Two modes: observation (simulates) then live (applies and pushes to Shopify), going live staying a human decision. Guardrails: never sell at a loss, outlier offers (< 60% of our price) ignored, pair/unit normalization. 6 families live, ~300 prices realigned; the rest adjusts on its own at each Wiser update.
-
An app that reads supplier price lists for me
Every supplier price update (a PDF or a ‘new product’ email) meant manual work: read it, find the product in Odoo, check EAN/SKU, key in buy and sell prices. An internal app (‘Product Update & Creation’) automates the pipeline: PDF upload or watching a read-only mailbox, EAN/SKU/price extraction via a Claude model, matching against the Odoo base, duplicate detection before creation, systematic human validation and traceability. A deliberate guardrail: no created product is ever published online automatically.
-
A pricing-system overhaul discovered by testing it
A per-variant pricing-system overhaul had been in preparation for weeks. While testing the price-update app, a gap between the price written in Odoo and the price synced on the merchant site revealed the overhaul was already in production — without formal confirmation. Each variant now has its own sale price, removing the cross-variant contamination risk. The app was fixed to write to the new field, and the matter escalated to the ERP integrator. Lesson: test in the real system rather than trust the docs.
-
Customer order status: invoiced, paid, delivered — three badges instead of one
Nothing clearly separated the invoice is out, the customer has paid and the goods are delivered. Three independent badges (Invoicing / Payment / Delivery) replace the merged status: color coding, deposit rate shown, automatic switch from remaining-to-collect to remaining-to-deliver, delivered lines greyed out. Transposed from the existing supplier module; two latent calculation bugs fixed along the way.
-
The Cobra App Store keeps industrializing
A synthesis across 5 sessions: Cobra's internal app hub goes, in a few weeks, from a few isolated critical apps to a genuine small standardized ecosystem — identical header everywhere, shared Odoo connection, refresh on a common cron. Two incidents (an overwritten version, a cron missing its env vars) caught within minutes thanks to the backup/compare discipline before every deploy.
-
Odoo pricing-system overhaul (cobra_price): a single source of truth
The Odoo pricing model was stacked and fragile: an auto-computed web pricelist, overlapping lists, a hard-coded 20% VAT, margin dropping to 0 the moment a product went out of stock. A single cobra_price field becomes THE source of truth via a _price_compute override — cost and margin recomputed, Omnibus-compliant strikethrough prices, immediate Shopify sync. 6 modules touched, ~7,300 products migrated, with real post-deploy follow-up (a display bug fixed the same day, 492 promo products re-pushed).
-
An integrator code review handled in full, point by point
After a Cobra change to an Odoo module, the integrator (Irokoo) came back with 6 technical points (security, reliability, consistency). Each evaluated individually: 3 fixed as recommended, 2 with an explicit trade-off (keeping the chatter visibility Hugo cared about, while neutralizing the risk another way), 1 deliberately declined. An unreported bug caught and fixed along the way. Deployed in an isolated Git worktree so as not to interfere with another job in progress.
-
A competitive price-tracking dashboard built in-house, rather than an integrator quote
The most direct build-vs-buy case of the period: a spec for a competitive price-tracking dashboard (ABC scoring, rules engine, price history), estimated at 3-4 weeks of dev, sent to the integrator in March 2026 — left at to-be-validated-before-development, never started. The most technical brick (price import/matching via Wiser) was already running in production; the control layer was missing. Built in-house with Claude Code, in a few days, on our internal app hub.
-
A €200,000 supplier backlog cleared in a week, line by line
A statement from a large supplier (GDD) showed a significant unpaid balance, spread across dozens of invoices — and didn't always account for the latest payments on the Odoo side, creating a double-payment risk. Systematic reconciliation of supplier statement / Odoo / bank statement on each new statement, six payment batches tracked one by one to actual bank confirmation: €200,059.33 settled in 6 transfers, two discrepancies (−€60, +€18) flagged to the supplier for correction.
-
Sales Performance view overhaul: merging Charge & Perf, dark mode
The monthly sales-performance page existed but stayed passive — a table to consult at month-end. Reworked into a daily tool: merging three sources into a single Charge app (monthly perf, actionable follow-up, operational load), ranking vs prior-year target live from Odoo, Shopify revenue separated from individual revenue, 1,817 dormant quotes cancelled in bulk, dark/light checked everywhere. In testing before switching to production.
-
The invoice agent goes to production: autonomous on Scaleway
Cobra's supplier invoice processing agent now runs on its own on a Scaleway instance: it reads email every 15 min, extracts and links each invoice to its Odoo purchase order (guaranteed 3-way match), and pushes it for approval in Teams. ~9-10 hrs/week saved — and above all a workflow that no longer drifts.
-
Product AI agent — from one-shot script to dashboard CDC
We created the 36 Davis variants by hand, in a Python script. Rather than starting over for every new brand, we formalized the method: a conversational AI agent on the Cobra dashboard that reads any source file and creates or updates Odoo products with no technical step.
-
Davis catalog → Odoo: price-list extraction + creation brief (Krypton & Ariane)
Preparing the integration of a new speaker brand (Davis, Krypton + Ariane ranges) into Odoo 18: a clean extraction of the supplier price list into 11 models / 36 variants, and a Claude Code brief — read-only first, create only after a green light. Nothing created in the database yet — deliberately.
-
HF-OS: a Next.js 16 + Payload 3 foundation deployed, admin login via Google
Bootstrapping then shipping the HF-OS technical foundation (Next.js 16 + Payload 3, Scaleway PostgreSQL, Render hosting), with admin login via Google SSO restricted to an allow-list. No business collections yet — just the deployed shell.
-
Re-linking a Shopify product to Odoo: a LINK/RELINK wizard in cobra_shopify
Odoo↔Shopify links broke when a product was recreated with variants (orphaned history). After a script rescue (Focal Bathys MG), we made it a feature: a LINK/RELINK wizard in cobra_shopify — SKU matching, atomic swap, no script.
-
Odoo → Shopify: product archiving and re-listing finally in sync
The connector reflected neither archiving nor re-listing of a product. 3 bugs fixed in cobra_shopify + a cleanup script (~590 stale records purged, 2 still-purchasable products made unavailable).
-
Claude context files for Cobra: update + CLAUDE-dev split
The context files for the Cobra dev Claude project were outdated. Factual update from the repo, split of CLAUDE-dev (generic core vs Cobra extension) and a CLAUDE-* naming convention. PR #385 to preprod.
-
Fable 5 reviews the site: 4 bugs, RSS, and an AI watch finally visible to LLMs
First full-scale test of Fable 5 the day after its release: complete site audit, 4 bugs fixed (counters, EN search index), the AI watch rendered as static HTML for AI crawlers, RSS feeds and a weekly consistency check — all shipped to production within the session.
-
Bilingual Knowledge Hub: English version + auto-translation
Making the Knowledge Hub bilingual FR/EN: a /en/ mirror of all 74 pages, hreflang, language switcher, bilingual search and glossary — plus a GitHub Actions workflow that translates each new FR page via the Claude API.
-
Custom Claude instruction system (CLAUDE.md + extensions)
Standardizing Claude's behavior across all my projects and two accounts: a universal CLAUDE.md + strategy and dev extensions. Triggered by an Odoo production incident that got hardcoded as a firm rule.
-
HiFi Lovers Instagram Strategy — Brief for Marine
Laying out an Instagram strategy from scratch for HiFi Lovers: 70/30 archive/editorial positioning, 4 content pillars, calendar, 8-week launch plan — before handing it off to Marine.
-
Sony Bravia II price update + zero-margin diagnosis
19 Sony Bravia prices updated in bulk via XML-RPC, then a diagnosis of a 0% margin: the UI was showing sellers_first_price under "Cost," not the actual standard_price.
-
Sogetronic profile: dropshipping stock import by supplier code
Extending cobra_import_stock_drop to match Sogetronic on the Sage Code (not the EAN). Schema migration, anti-duplicate XML seed, cherry-pick preprod3 → main.
-
Claude setup: documentation, onboarding, and Knowledge Hub
Documenting the Claude setup logic (.md files, projects, two accounts) to share with a friend just getting started — and to build on session after session.
-
PPTX oral presentation "Teen Addictions" (Damien's brevet)
Turning a 9th-grader's script into a presentation for the brevet oral: 9 "icy cyan" slides, sourced stats, integrated photos — without flattening the teen's voice.
-
Alexis's English PowerPoint — "The Secrets of My Success"
A narrated 10-slide PowerPoint + script timed to the second for an English class project (Dual Diploma). Iterative workflow with visual QA slide by slide.
-
This Knowledge Hub itself
A static GitHub Pages site (HTML/CSS, zero framework): AI portfolio, operational journal, and GEO reference. One page per entry, llms.txt + JSON-LD authorship.
-
GSC diagnosis + JOIN Stories JSON-LD fix + BigQuery setup
7 product pages with "product snippets" errors in GSC. Root cause: JOIN Stories injects implicit Product entities. Non-invasive snippet fix + BigQuery setup.
-
Epson sales declaration: Odoo export → Google Sheets
An Epson declaration covering 7 promo periods and 10 projector SKUs, despite supplier SKUs missing from Odoo. Mapping via supplierinfo, formatted Sheets export.
-
Double Claude Code: Cobra vs HL
Two Claude Code instances: the Cobra account (Odoo/Shopify dev) and a new HL account (personal, strategy, Knowledge Hub). Both can write to the same journal.
-
Speech & job description for Cobra store sales associate
Turning a raw management speech into three actionable deliverables (bullet points, prose, Word job description to sign) following a team restructure.
-
CDC-18 stabilization: dashboard filters, menus, fr_FR translations
Two leftover bugs in the purchasing dashboard: buttons not activating filters, and menus still showing old FR labels. Layered diagnosis, immediate fix + long-term fix.
-
Cobra UI audit + odoo18_design_reference update
Comparing the theoretical Odoo 18 reference against the actual code across 9 cobra_* modules. 35 XML files read, 5 technical debts identified, ~60 custom fields inventoried.
-
Autonomous supplier invoice processing agent
Scoping the full architecture of an invoice agent (5 channels, line-by-line matching, 4 sub-agents, Teams actions) before writing a single line of code. Touch Odoo only once a week.
-
Automatic Odoo product creation agent
Automating Odoo product creation through multi-source triangulation (POS Excel, email screenshot, price photo). First pattern tested on the Sony Bravia FY26 catalog.
-
SFTP server + automatic dropshipping stock pipeline
SSH hardening (fail2ban, ufw, chroot) + script that feeds any dropped file into Odoo via the existing module. Hooking into action_run_import: ×60 speed gain.
-
PO email routing Drop vs. Restock + Cobra templates
Routing PO confirmation emails to the right Cobra template based on Drop (direct delivery) or Restock (warehouse), with _send_confirmation_mail override. In production.
-
Dynaudio Emit II sales analysis: Shopify + Odoo cross-referenced
Cross-referencing Shopify (web channel, 104 orders) and Odoo (all channels, 186 units, +79%) for an accurate sales picture. The limits of Drive MCP for file editing.
-
Claude Code mission brief: D&M France invoice verification
14 PDF invoices imported as Odoo drafts, unreliable. A structured, secure brief (PO matching, WEEE, discount, guardrails) so Claude Code can work autonomously.
-
CDC-18 form view: surgical production deployment
Pushing only the PO form to production (buttons, dynamic titles, statusbar) without pulling in CDC-19 — isolating a clean commit from a mixed preprod3 stack.
-
Delivered / Invoiced / Paid statuses on purchase orders
3 consolidated statuses (Delivered/Invoiced/Paid) as badges on the PO form and list views, so you can see a order's real state at a glance. Multi-list xpath pitfalls.
-
CDC-19: improved purchase order list view
Drop/Restock badge, confirmed delivery date, time-stripped dates in the PO list. Two OWL 18 traps: position=attributes ignored, silent XML rollback.
-
CDC-18: Cobra purchasing workflow (cobra_purchase)
A full purchasing module for Cobra: RFQ/PO dashboards, supplier response detection, warehouse filters. 6 Odoo 18 SaaS bugs turned into 7 reusable rules.
-
Sogetronic seed + Claude Knowledge Hub restructure
Two needs in one session: loading Sogetronic Sage Codes onto 175 product records, and restructuring Claude context files for dual chat + Code usage.
-
Cobra SFTP infrastructure: phase 1 server setup
Setting up a durable SFTP infrastructure (Scaleway/Ubuntu) where each supplier drops their stock files, automatically picked up by Odoo. Step-by-step server setup.
-
cobra.fr GTM overhaul: purge 71 → 20 tags + Consent Mode v2
71 accumulated tags, outdated CMP, patched-together Consent Mode. Migration to native Shopify Consent Mode v2, purge down to 20 tags, ~70 orphan variables removed.
-
Shopify collections SEO fix (Guillaume's audit)
11 systemic issues across ~175 collections after a mass optimization. 182 "| Cobra.fr" suffixes removed in 26 GraphQL batches, 0 errors. Post-compaction recovery.
-
Purchase order email templates overhaul (FR + EN)
Bringing the PO template up to the level of the "payment" template, in two languages, with fixed-text constraints. Formatting only — zero back-and-forth on the content.
-
Anatomy of Special Issue Collector #1 cover — HiFi Lovers × Yamaha
Structuring the visual hierarchy of the first special issue cover, drawing on the visual grammar of 80s–90s Marvel/Image comics (corner box, masthead, collector badge).
-
Structuring the Claude "Odoo" project: ecosystem reference docs
Consolidating all validated technical connections into a reference doc so every new conversation starts with the right context.
-
Yamaha special issue gifted to advertisers — Brevo × Shopify
Giving away the first HiFi Lovers special issue to advertisers with a clean mechanic: Excel list → Brevo → Shopify combo promo codes restricted by segment AND product.
-
Audit & filtering of the Cobra mailbox (Outlook)
Getting back on top of the hlahutte@cobra.fr inbox drowning in noise (Odoo catchall, EDI, notifications): 30-day audit, server/client rules, urgent backlog.
-
INPI trademark management — HIFI LOVERS
Taking back control of the HIFI LOVERS trademark (already filed with INPI without my knowing) and preparing a supplementary figurative filing + class 16 for print.
-
Contesting a Roadsurfer / Creditreform debt claim
Contesting a €2,549 claim (disputed scratch on a rented van) all the way to filing with CEC France: multilingual FR/DE drafting, navigating debt collection interfaces, compiling supporting documents.
-
Audit & launch of the Haute Fidélité Shopify store
Auditing and finalizing the HF Shopify store before scaling: MCP Shopify, GLS switchover, email authentication, 4 editorial templates, audit of 30+ products and 7 collections. (Merged from 3 sessions.)
-
Setting up Adrien's sole proprietorship (carpentry) — INPI filing
Helping my 18-year-old nephew start his carpentry sole proprietorship: guides, 9-step INPI filing, supporting PDF documents, choosing the right tax regime.
-
Shopify/Odoo audit: 803 products, 3 months of work
Cross-referencing the Shopify catalog (front-end) and Odoo (back-end): SKU consistency, prices, stock, metadata across 803 products. The B&W AM-1 pair vs. single unit case.
-
Sendcloud × GLS config for Haute Fidélité Shopify
Sharing HF's e-commerce logistics with Cobra's infrastructure (Sendcloud + daily GLS pickup) while keeping customer tracking on-brand for HF. Real-time guided setup.
-
Docs & billing for Salon Haute Fidélité Paris 2026
Streamlining the admin for the 2026 HF Show: replacing the formal contract with a Qonto invoice + bilingual participation terms, for 20–30 exhibitors.
-
Daily HiFi news Telegram bot
A Telegram push every morning with global hi-fi news: ~35 multilingual RSS sources, copy written by the Claude API, duplicate memory, GitHub Actions cron — built from scratch.
-
Colleagues getting on Claude
Claude isn't staying a solo tool: colleagues at Cobra are starting to use it. Sharing context without credentials, writing a good CLAUDE.md, avoiding reinventing the wheel.
-
Claude arrives in the Cobra workflow
Before Claude, Odoo dev meant doing it by hand: OCA forums, docs, trial and error. The pivot — treating Claude like a senior colleague who amplifies, not replaces.