Skip to content

harshit1garg1/odoo-personal-work-manager

v0.3.0

Manage your Odoo work with direct API calls from your own execution environment. No mandatory Odoo addon or hosted connector.

Odoo Work — 0.3.0

Manage your Odoo projects, tasks, assignments and timesheets from your own execution environment. No mandatory Odoo addon, hosted connector or server deployment. A bundled Node.js helper reads private configuration, makes direct API calls and exits.

Start here

Requires Node.js 24+, an execution-capable host, network permission to your Odoo instance and access to its external API. Odoo 19 JSON-2 is the initial target. Other versions and customer modules need their own compatibility testing.

  1. Run npm ci from the unpacked plugin folder (for the standard archive, use npm ci --omit=dev).
  2. Copy config.example.json to a private location outside Git. Enter your Odoo HTTPS base URL and personal API key there. Add the database name when your instance requires it. The file is plaintext; protect its permissions.
  3. Invoke the helper with the private file path. Supply operations as JSON on stdin, never keys in arguments or chat:
'{"operation":"describe"}' | node scripts/odoo.js --config "C:\Private\odoo-config.json"
'{"operation":"list","args":{"concept":"task"}}' | node scripts/odoo.js --config "C:\Private\odoo-config.json"
'{"operation":"dashboard"}' | node scripts/odoo.js --config "C:\Private\odoo-config.json"

The dashboard command creates a private, read-only local HTML report and returns its path. Open that file using your execution host. It does not start a web server or expose data publicly. For a sample report without credentials, use --demo --output C:\Private\sample.html instead of --config.

Read direct access for confirmation, private state, custom mapping and failure handling. Local Codex is the first test target. Ordinary ChatGPT chats without command execution cannot run this helper. ChatGPT Work and cloud environments need host-specific validation; installation alone does not grant execution or network access.

Changes require review

Use prepare to obtain the exact record, company, acting user and proposed values. After the user approves that preview, send execute with its operation ID and confirmed:true. Report success only from a verified receipt. A lost response can leave the write uncertain; inspect result and reconcile the same operation. Never automatically repeat a potentially committed create.

Receipts and private fallback todos/notes are scoped to Odoo origin, database, acting user and company in local SQLite storage. They can contain confidential work data. No credentials are stored in that database. A config file or environment variable is not encrypted by this plugin. Do not commit keys even in a private repository.

Optional organisation module

The separate free odoo_work_assistant download can be installed by an organisation in its own Odoo 19 staging or production environment. It provides existing company mappings, private models and operation support. It is not needed for the standard helper. Read custom modules.

Company-specific governance and presentation customisation is available by enquiry; no new organisation controls or fixed price are promised by this release. Every employee remains subject to Odoo permissions. ChatGPT/Codex workspace installation policies belong to those platforms.

Development and verification

npm run build
npm test
npm run package

The build and existing HTTP demo/MCP tests exercise the legacy optional integration; the normal helper does not require that HTTP server. Maintainer ZIP packaging uses Windows PowerShell/.NET. Validation distinguishes automated coverage from live deployment evidence. Publishing describes the separate directory review process.

Independent project by Harshit Garg, not affiliated with Odoo S.A. or OpenAI.