— Japanese homepage is fully in Japanese
- Menus, footer, approval demo, and theme toggle on /ja now use Japanese labels — not a mix of English chrome and Japanese headlines.
Public product notes for the hosted Odoo MCP gateway: governance, connectors, and console updates.
Changelog — ERPipe hosted beta
Product updates
— Japanese homepage headline stays in its column
- The Japanese landing page no longer lets the headline run over the approval card, and the demo buttons on that card are in Japanese.
— Audit log no longer looks like writes are stuck waiting
- Each write now shows one final result instead of a leftover “waiting” row after it already ran.
- While an assistant checks whether you have approved, those check-ins no longer clutter the audit list.
- If you reject or a request expires, the audit line updates to match — you will not see a waiting badge with an empty Approvals inbox.
— Japanese landing page and documentation now live
- Visitors can now explore ERPipe in Japanese at /ja with tailored explanations of human approval write gates and enterprise AI safety.
- A quick language toggle is now available in the navigation bar to easily switch between English and Japanese.
— AI assistants now see your latest guides
- The machine-readable content map that AI assistants (ChatGPT, Claude, Gemini) read to discover our documentation now reflects the current guide library and comparison pages, with a fresh as-of date.
— Totals no longer trip up your AI
- When your AI asks for a grand total (sum, count, average) it now gets one clean number back instead of an error telling it to group first.
- Grouped breakdowns work exactly as before — and if the AI forgets to say how to group, the error now shows it the right way to ask.
- Asking for a record count now works on every Odoo version we support — older servers no longer reject the request.
— Odoo webhooks are now actually easy to turn on
- Each connection now shows a 5-minute, click-by-click recipe for creating the Odoo automation that feeds events to your AI — including the exact field to add, since Odoo cannot send custom headers.
- A new Test webhook button queues a sample event so you can confirm end-to-end in seconds: press it, ask your agent to run list_odoo_events, and see it.
- The connection page now shows webhook status at a glance — waiting for the first event vs working, with the time of the last event.
- Behind the scenes, events can now authenticate the way Odoo actually allows (secret in the payload or URL), and the secret is never stored in the event log.
— A clearer first run, and a safer default for your Odoo login
- The connections page now opens with the three setup steps in order, so the workspace address for AI clients appears once you actually have an instance to use it with
- The Odoo user field no longer suggests your administrator account, and the setup step explains what happens to the credential before you type it
- The setup guide now says which client plans can run MCP tools, so you can check that before blaming the connection
- Setup progress is now recorded per workspace, so we can see where people get stuck and fix the real step
— Guides, tools, pricing, and about now follow the homepage story
- Each page now opens with a clear claim and supporting proof, followed by the same measured runway used on the homepage
- The complete guide library, hosted tool catalog, beta pricing details, and company background remain available in their new layouts
— Every public page now has dark mode and a working mobile menu
- Guides, pricing, legal, comparison and connector pages share the same header and footer as the homepage — including the theme toggle, which these pages did not have before
- On phones there is now a real slide-out menu with every site link instead of a cramped row of links that did not fit on small screens
- Public pages download much less code on a first visit, so guides and articles open noticeably faster
- Buttons, form fields, badges, switches, menus and confirmation dialogs across the workspace and marketing desk now use the same component system as the homepage, with consistent keyboard navigation and focus handling
— The ERPipe logo is back in the homepage header
- The homepage header shows the full ERPipe logo again — it had been replaced by a small square during the landing page rebuild
- The logo switches to its light version automatically in dark mode, like the rest of the page
— The landing page is rebuilt, faster to read, and now supports dark mode
- The homepage is rebuilt around the approval gate, so you can see exactly how an AI write to Odoo is paused for your decision before you ever connect
- The page now offers a dark and light theme, remembers your choice, and follows your system preference on a first visit
- It is faster to load and easier to read on phones, with larger text, clearer contrast, and real product controls instead of diagrams
— Link previews now show how agents connect to live Odoo
- When you share most ERPipe pages in chat or social apps, the preview image now shows AI agents connecting through the hosted gateway to live Odoo, with human approval and an audit trail
- Each guide still uses its own article preview image
— Telegram approval messages now show which Odoo instance
- Write-approval messages in Telegram now name the Odoo instance, so you can tell a test database from production before you approve
- Production-like instance names are marked clearly, matching the existing approval email
- After you approve or reject, the short status line also includes the instance
— Your analytics choice is back, and comparison pages now open complete
- The analytics choice is offered again. It had stopped appearing, which also stopped ERPipe recording where a new workspace first came from — so recent signups have no source recorded and that gap cannot be recovered
- You can now allow or decline analytics independently of whether Google Analytics is switched on, and declining still stores nothing
- The connector setup page and the comparison, alternatives, and compatibility pages now include their full text in the first page response, so search engines, AI readers, and text-only browsers no longer see a short summary
- Every public page now links onward to related pages, and the Odoo compatibility table is read from one shared source so the page and the machine-readable version cannot disagree
- Each guide now publishes its questions and answers in a form search engines and AI assistants can quote, and the two setup guides publish their steps the same way
— Guides now arrive complete and share with their own image
- Every Odoo × AI guide now includes the complete article in the first page response, so search, AI readers, and text-only browsers do not need JavaScript to reach the body
- Each guide now has its own share image, while the Guides page describes the complete seven-article collection consistently
— Guides now separate setup, field notes, and Odoo AI changes
- The Guides page is now an Odoo × AI field manual, so you can tell repeatable setup from implementation experience and official-source analysis before opening an article
- New notes compare native Odoo AI agents with an external MCP gateway and explain when a local process, Odoo addon, or remote gateway fits
- The human-approval guide now explains why Odoo permissions remain essential and why AI writes still need a narrower decision path
- Claude Code now has a focused setup guide for browser sign-in, shared or personal configuration, and a safe first Odoo check
- A new guide explains how agents can reuse a short lesson from a verified fix while still checking live Odoo every time
— Approved Odoo writes can finish safely even after a lost response
- For supported Odoo actions, your agent can show a preview, wait while an owner approves in the dashboard, then continue the same request
- If the first response is lost, retrying the approved request returns the completed result without applying the Odoo action twice
- Changed or expired approval details are rejected before they reach Odoo
— Campaign visits can now be followed through a working Odoo connection
- If you allow analytics, ERPipe keeps one bounded campaign source and referring hostname, then measures aggregate progress from signup to first Odoo connection and first successful tool
- Campaign labels reject email-like values and never include full referring URLs, Odoo data, credentials, or record details; choosing Continue without analytics before starting sign-in creates no attribution row
- The homepage, About page, guides, pricing, changelog, and open-source lineage are now easier to find and use one clear product description
— Analytics now waits for your choice
- ERPipe does not load Google Analytics until you choose Allow analytics
- You can continue without analytics or change the choice later; signups are now counted separately from returning sign-ins
— The tools page now starts with the read-only checks most people need
- After you connect an agent, the tools page and ChatGPT setup guide now start with a live receivables-style check, then drill into one company
- The full list of tools is still there. Writes still stay off until you turn them on, and they still wait for your approval
— ChatGPT setup is easier to find from the connector guide
- The connector setup page now shows the five ChatGPT steps up front and links to the full how-to
- The steps work over a hosted connection, so you do not run a local MCP process on your laptop
— Agents can read larger Odoo files
- Your agent can now pull Odoo files up to about 10 MB instead of 2 MB
- Files bigger than about 15 MB still need to be opened in Odoo
— Approval previews follow the language you are using with the agent
- The approval card, email, and Telegram note for each request follow the language you are using with the agent, including the why text and the actions on that request
- Existing requests keep the language they were created with. The rest of the dashboard does not switch
— The guides index is readable without JavaScript
- The Guides page now lists every guide and comparison even if JavaScript is turned off
- Search engines and text-only browsers can read the same titles and short descriptions as the interactive page
— Privacy, terms, and security pages are readable without JavaScript
- Privacy, Terms, Security, DPA, and Subprocessors now show their full notices even if JavaScript is turned off
- Search engines and text-only browsers can read the same trust-center text as the interactive pages
— Connection health emails open the right settings page
- The Open connection settings button in up/down emails now opens that Odoo connection instead of a missing page
- Older emails that used the instance name in the link still work after you sign in
— About and pricing pages are readable without JavaScript
- The About and Pricing pages now show their full notes even if JavaScript is turned off
- Search engines and text-only browsers can read the same founder and beta-price details as the interactive pages
— Public changelog notes are readable without JavaScript
- The public changelog page now shows recent product notes even if JavaScript is turned off
- Search engines and text-only browsers can read the same notes as the interactive page
— Send feedback sits quietly at the bottom of the workspace menu
- The signed-in menu is English-only. Send feedback is a small action under the page list, not another Admin item
- It still opens a short note about ERPipe Cloud. It is not an Odoo support ticket
— Send product feedback from the signed-in workspace
- There is a Send feedback control in the signed-in workspace so you can report a bug or idea about ERPipe Cloud
- Your note goes to the ERPipe team with the page you were on. It is not an Odoo support ticket and there is no in-app reply thread
- Do not include passwords, keys, or personal records. The privacy notice now explains how this feedback is stored
— Sign-in page is no longer treated as the homepage
- The sign-in page now tells search engines not to index it
- It no longer points search engines at the public homepage by mistake
— Public pages keep their layout on refresh
- The marketing site no longer drops to plain unstyled text after you reload
- If a tab still looks broken, refresh once so it picks up the restored styles
— Public list of every hosted Odoo MCP tool
- There is now a public catalog of the 43 tools your AI client can call on the hosted connector, including which ones exist only on hosted ERPipe
- Guides that explain what an Odoo MCP server is, how to connect ChatGPT, and how write approval works now lead with dated facts and comparison tables
- Search engines and assistants that do not run JavaScript can read the catalog and those guides from the first HTML response
— Public pages now readable without running the app
- Search engines and AI assistants that do not run JavaScript can now read the product definition, FAQs, and guide text on the public site
- Missing pictures and leftover files no longer pretend to be the homepage
- The hosted tool count on the site matches the live connector (43 tools)
- New comparison page: ERPipe versus Pantalytics, with unknowns marked and no invented scores
— Record totals are no longer a short search page
- When an agent asks how many records you can see, it now uses the full access count instead of a search page that stops at 50
- Reconnect your AI client so it picks up the corrected lookup path
— Stale write approvals time out on their own
- A write request that sits unapproved, or approved but never finished, now expires after a short wait instead of hanging in Approvals
- If a write was already running and got stuck, it is marked unclear rather than left in progress — check Odoo if you are not sure it applied
- Reconnect your AI client so it looks up records the supported way, which avoids a common class of failed searches
— Approve or reject a write from the email
- Approval emails now have Approve and Reject, like Telegram
- Tapping a button opens a short confirm page that applies the decision. You do not need to sign in or open the dashboard first
- Review details is still there if you want the full inbox. Do not forward the email — those buttons decide the write
— Limit which Odoo models an agent may use
- On each connection you can now list the models and operations an agent is allowed to read or change. Leave the list empty to keep the current open behavior
- You can save short named actions for allowed Odoo methods so agents call those instead of inventing their own server scripts
- Writes still start off and still need your approval when you have turned that on
— Clearer answers for connecting AI agents to Odoo
- A new About page explains who built ERPipe and why a hosted, approval-first path exists
- The ChatGPT setup, build-versus-buy, and alternatives pages now lead with a direct answer and common questions
- New pages cover what an Odoo MCP server is, how write approval works, and when a custom server still makes sense
— GitHub sign-in is paused for now
- Continue with GitHub is temporarily unavailable on the sign-in page
- Use Google or an email sign-in link to get back into your workspace
— Agents can reuse verified past fixes without being asked
- ERPipe now guides connected agents to look up similar past cases when a problem looks familiar — you do not have to ask them first
- After a verified reusable fix, they can save a short lesson for next time, not passwords, secrets, or one-off lookups
- Ask them to forget a saved case if it is wrong. Reconnect the agent if it still ignores past cases
— Telegram approval cards update when you decide in the dashboard
- Approving or rejecting a write in the dashboard also clears the Telegram approval buttons
- You get the same short confirmation in Telegram, including on other linked owner chats
- Tapping Approve or Reject in Telegram still updates every card for that request
— Workspace owners control connection settings
- Only the workspace owner can create, edit, pause, or delete Odoo connections, change write settings or field rules, and rotate webhook secrets
- Teammates still see connections and can review and approve write requests
— Sign-in codes are protected from guessing attacks
- Too many wrong code entries blocks that email for a short time and cancels its outstanding sign-in codes
- Each email address gets a limited number of sign-in messages per window to stop automated abuse
— Saved agent memories stay private to you
- Each person's saved cases stay in their own workspace account — teammates do not see them
- Agents only bring back closer matches, so unrelated past work is less likely to appear
— Agents load less of your Odoo data by default
- Agent lookups now need a search filter instead of dumping an entire table
- Each lookup returns a smaller page of rows so chats stay faster
- If an agent asks for too many rows at once, we trim the request automatically
— Choose how you get write-approval alerts
- In Settings → Notifications you can turn email, Telegram, and browser push on or off independently
- Everything stays on by default. Turning a channel off pauses alerts without unlinking Telegram or this browser
- Enable this browser from the Approvals inbox; manage all channels from Settings
— Approve in Telegram with one tap
- Tapping Approve on a Telegram approval card now approves immediately — no second confirmation tap
- Reject is still one tap. Dashboard Approvals still asks you to confirm before deciding
— Telegram approvals leave a short confirmation
- After you approve or reject a write in Telegram, the long approval card is removed from the chat
- You get one short confirmation instead of a second long message
- Approval alerts no longer expand with a large website preview
— Telegram approval buttons now reliably appear
- Fixed an issue where Approve and Reject buttons were silently dropped by Telegram, causing approval notifications to never arrive
- Buttons are now compact and stay within Telegram's size limits — no changes needed on your end
— Telegram bot linking now works reliably
- Fixed a silent failure that prevented Telegram from pairing after you sent /start — bot tokens are now stored correctly
- The Settings page now warns if your bot is shared with another webhook so you know to create a dedicated bot in @BotFather
- A live webhook check runs at connect time; if your bot is already claimed by another service you'll see an 'overridden' badge instead of a silent failure
- Pairing status updates automatically after you open the connect link — no need to refresh the page
- If you set up Telegram before this update, go to Settings → Notifications → Disconnect, re-paste your bot token, save, then click Connect Telegram and open the link (do not type /start manually)
— Clearer Odoo errors and connection health tracking
- Agents now get a short hint when a lookup or write is blocked — including which methods are allowed, how to fix a missing group-by, and how to check field names for this Odoo version
- Count and group lookups on newer Odoo versions no longer fail on a bad count formula
- We now record why an Odoo connection is unhealthy (login versus host down) so we can later pause broken logins automatically — nothing is auto-paused yet
— Connect your own Telegram bot for approval alerts
- Each workspace now uses its own Telegram bot — create one in @BotFather, paste the token in Settings → Notifications, and ERPipe sets everything up automatically
- No shared bot or manual configuration required: webhook registration, encryption, and deep-link pairing all happen in the dashboard
- Approve or reject writes directly in your bot's chat with the same one-tap buttons as before
— Approve or reject writes directly from Telegram
- Connect your Telegram account from Settings → Notifications to receive write approval alerts in Telegram
- Each notification shows the operation, model, summary, rationale, risk level, and time remaining
- Tap Approve or Reject in the Telegram message — same authority as the approval inbox in the dashboard
- Approve requires a confirmation tap before executing, matching the dashboard confirm dialog
- Use /status in the bot to list pending approvals, /unlink to disconnect
— Agents wait briefly after you approve a write
- After you approve a write, connected agents now wait a few seconds for the result instead of stopping the chat
- If you need more time, the request stays in Approvals and the agent can continue later
— Approval cards show names on vendor pricelist lines
- Write approvals now show the Odoo record name instead of Unresolved name, including vendor pricelist lines that do not have a Name field
- The current value of each changed field is shown when Odoo can read the record
— Agents can remember solved Odoo work
- Connected agents can save a short summary of a solved problem and recall similar past cases later
- Saving a remembered case works after a normal Odoo lookup — the agent can cite the step it just ran
- Looking up a similar past case now works in live workspaces after a case is saved
- Recalled memories are labeled as untrusted history — agents still re-check live Odoo data before acting
- You or the agent can forget a saved memory when it is wrong or outdated
- Signing in and reconnecting an agent stays on the fast path; remembering happens only when the agent saves or looks up a case
- Platform admins can review and forget agent memories across workspaces from the admin console
— Optional browser alerts for write approvals
- Workspace owners can opt in to browser alerts when a write is waiting for approval
- Each alert opens the pending request for review in the secure dashboard
- Alerts never approve a write automatically and can be disabled from the Approvals page
— Beta interest confirmation email
- Joining the priority beta list now emails a confirmation with a free Connect Odoo link
- Platform admins get an alert when someone joins from the landing page
- Landing form success copy points people to their inbox
— Platform ops console: monitoring, audit, email log
- Admin navigation adds Monitoring, Audit, and Emails
- Outbound transactional emails are logged (kind, recipient, subject, provider, result — no bodies)
- Cross-tenant MCP audit stream for platform admins
- Connection probe fleet view with down/up status and alert state
— Pricing page + canonical public-content workflow
- Human-friendly Pricing page with Free Beta limits, planned tiers, and signup CTA
- Pricing and changelog share canonical JSON with generated Markdown mirrors
- docs:check fails CI when generated public content drifts
- README defines the release workflow for humans and AI agents
— Security & Trust + universal AI-agent setup
- One setup prompt for ChatGPT, Codex, Claude Code, Gemini, Antigravity, Grok, and other MCP clients
- Human setup recipes remain available from the same canonical connector guide
- Security & Trust page now documents the full Odoo credential boundary and owner controls
- Large audit payloads are redacted before preview truncation
- Production dependency audit has no high or critical findings
— Dashboard, marketing, and beta onboarding refresh
- Redesigned tenant dashboard and marketing operations views
- Landing beta-interest form persists submissions before confirming success
- Privacy notice covers beta-interest data and its 12-month retention period
- Long connection values stay contained on narrow screens
- Social login button contrast restored
— Authentication and connection-control hardening
- Trusted ERPipe hosts accepted by cookie CSRF checks
- New-user alerts tolerate runtimes without an ExecutionContext
- Connection detail split into focused controls with shared UI primitives
— Stability pass — HITL email, PII presets, LP wizard, compat matrix
- Owner email when a write approval becomes pending
- One-click PII field-policy presets on connection detail
- Least-privilege checklist step in the connection wizard
- Public Odoo 16–19 compatibility matrix at /compatibility
— SEO / GEO foundation + GA4 + content cluster
- robots.txt, sitemap.xml, llms.txt, pricing.md, security.txt, and OG image
- JSON-LD for Organization, SoftwareApplication, FAQ, HowTo, and BreadcrumbList
- GA4 SPA page views, CTA events, and lead generation
- Guides, build-vs-buy, alternatives, and machine-readable content mirrors
- www redirects to erpipe.com; IndexNow key published
— Workspace multi-instance MCP
- One workspace MCP endpoint with explicit instance keys on Odoo tools
- Cross-instance read fan-out where enabled
- Dashboard connection model aligned to instances
— Trust pack + hosted beta console
- Security, privacy, terms, DPA, and subprocessors pages
- Magic-link auth, approvals, audit, and usage views
- Isometric marketing landing
Last updated: 2026-09-04