Meet Archimedes. Turn your โEureka!โ into a patent disclosure.
An AI patent plugin for Claude Code, Codex, and OpenCode. Archimedes orchestrates specialist agents across research, ideation, drafting, review, and diagramsโwith traceable, forkable decision paths.
Run these commands in your patent workspace. Setup writes editor configuration; see installation behavior before using an existing workspace.
npm install -g oh-my-patent
oh-my-patent adapt setup --workspace-dir .Open that workspace in your AI coding tool, load the generated integration, and start with:
/archimedes
> Create a patent project about homomorphic encryption in privacy-preserving computing.
Use --tool claude-code, --tool codex, or --tool opencode to configure one
platform. Without --tool, setup targets all three. See the
platform notes if the entry point is unavailable.
For AI assistants helping users install this
Choose the user's patent workspace, review the installation behavior above, and run:
npm install -g oh-my-patent
oh-my-patent adapt setup --workspace-dir .
oh-my-patent check --workspace-dir .Then help the user load the integration and start a project with /archimedes.
| Capability | What it gives you |
|---|---|
| Coordinate specialist agents | Research, ideation, patentability assessment, drafting, review, and technical responses under one orchestrator |
| Keep decisions traceable | Saved rounds, scores, innovation snapshots, and reasons in .brainstorm/; branch from a recorded node or restore an idea |
| Resume recorded work | Workflow state in .patent/state.json and agent outputs in references/ provide context for continuing a project |
| Generate patent figures | Mermaid or PlantUML sources rendered to SVG and PNG, with figure references inserted into MAIN.md |
| Inspect progress | CLI queries, Markdown reports, a terminal UI, and environment checks |
The project brings the disclosure, its supporting material, and its decision history together in one project directory. Rendering engines and retrieval services have their own setup requirements; see the usage guide.
Overview of the ten stages, grouped by purpose. Arrows back to research and drafting show where further work may be needed.
| Step | Workflow stages |
|---|---|
| Prepare and research | INIT โ RESEARCH |
| Develop and assess ideas | BRAINSTORM_R1 โ BRAINSTORM_R2 |
| Write and illustrate | DRAFT โ DIAGRAM_DRAFT |
| Review and revise | QA_LOOP โ FINAL_REVIEW |
| Refresh figures and finish | DIAGRAM_FINAL โ DONE |
Review can return to earlier stages. The workflow reference shows the supported transitions and explains scoring decisions separately from stage changes.
| Pattern | Purpose |
|---|---|
| Orchestration | Archimedes coordinates specialists and carries project context between stages |
| Adversarial brainstorming | Candidate ideas receive examiner-style challenges before selection |
| Parallel evaluation | Security, compliance, and patentability specialists assess different dimensions |
| Review and response | Reviewers raise issues; the technical responder proposes document changes |
| Decision recording | The path recorder preserves rounds for comparison, branching, and recovery |
The agent reference lists the 14 registered agents, 6 skills, 9 commands, and their roles. Actual dispatch uses the capabilities of the selected host.
| Read next | Contents |
|---|---|
| Usage and CLI | Installation, platform differences, all CLI domains, and uninstall behavior |
| Workflow | Ten stages, review loops, and threshold behavior |
| Agents and collaboration | Registered IDs, skills, commands, and collaboration patterns |
| Architecture and development | Four layers, repository layout, project files, and development commands |
| Documentation index | Bilingual guides and design references |
| Brand guide | Archimedes artwork and usage rules |
Contributions are welcome. Read CONTRIBUTING.md or report an issue. Licensed under MIT.
With thanks to the LINUX DO Community