Find the right questions
Propose a discovery scope, stakeholder roles, uncertainties and a linked interview guide. Revisit the scope as you learn.
prepare_discoveryA specialist for your AI workspace
AxWise brings structured product discovery to your agent. Turn a brief, selected research and interviews into personas, insights and a product plan you can build on.
Open-source extension. Local workflow. Your chosen model.
AxWise is the focused discovery extension inside it. This site is home to the open-source project, examples and standalone installation—not a second web app.
A useful specialist, not another orchestrator
Choose one capability, or ask your agent to connect the steps. Standard and deeper analysis are bounded options for the task you select.
Propose a discovery scope, stakeholder roles, uncertainties and a linked interview guide. Revisit the scope as you learn.
prepare_discoveryGenerate synthetic persona cohorts, simulate interviews and talk with an exact saved persona about a selected document.
generate_personas · simulate_interviews · chat_with_personaAnalyze interview quotations, themes, patterns, stakeholder sentiment and insights. Synthesize selected market sources and surface gaps.
analyze_interviews · research_marketCreate an evidence-linked PRD, preserve its history through revisions and propose a delivery brief with acceptance checks and open decisions.
create_prd · create_delivery_briefInside the loop
Goose, Codex or another compatible MCP host owns the conversation, tools and approvals. AxWise is called for a specific discovery deliverable—not for every message.
Explore the source“Local” describes where the workflow runs. Selected material is sent to the configured model; this is not an offline-inference claim.
Start with what you need
No special command language. Ask for the result you want in your normal chat. Your host chooses the tool and may ask you to clarify the scope.
“We’re building a booking tool for independent studios. Propose the discovery scope, stakeholder groups and interview questions before we decide what to build.”
“Analyze these selected interviews. Show themes, patterns, stakeholder sentiment and conflicting needs, linked to supporting quotations.”
“Create three synthetic personas from this scope, simulate the interviews, then let me discuss this exact draft with the studio manager persona.”
“Use this saved analysis and selected market evidence to create a PRD. Add onboarding requirements without losing the earlier ones, then prepare an outsourcing brief.”
Simulations are labeled synthetic. AxWise keeps their provenance with the resulting artifacts. Model-generated interpretations still need your judgment.
One engine, two ways in
The desktop bundles AxWise and its runtime. Enable the extension when you want its specialist capabilities, and keep working in the same chat.
Orqanix adds its own sign-in, model access and shared Results experience. Its service terms and model access are separate from the open-source license.
Get OrqanixTwo launch paths, the same engine. These commands use the versioned GitHub release artifacts—not an npm or PyPI registry listing.
Launch with npx
npx --yes --package=https://github.com/AxWise-GmbH/axwise-flow/releases/download/axwise-extension-v0.3.0/axwise-extension-0.3.0.tgz axwise --config /absolute/path/axwise.jsonOr launch with uvx
uvx --from https://github.com/AxWise-GmbH/axwise-flow/releases/download/axwise-extension-v0.3.0/axwise_extension-0.3.0-py3-none-any.whl axwise --config /absolute/path/axwise.jsonConfiguration and host examples ↗
npm archive · 157,987 bytes
a17caf788dd42e7979f281f2dce6aa3ec527ad6bd1b3a8c8a7f7b2d72c22fe20Python wheel · 152,383 bytes
d3c13786ce62de85a8e7dc6ef380c9cb0de61ca6b6477409133b579d36fe336fThe code is free to use and modify under Apache 2.0. Model-provider usage may incur charges. Standalone use does not require an Orqanix account.
Clear boundaries
No. It exposes specialist tools through MCP, not a per-message router. The host decides when to invoke a tool and retains its own permission system. Ordinary chat, weather, news, browsing and coding stay with the host’s normal tools. Tool selection varies by host and model; it is not a perfect intent classifier.
Workflow state and immutable Markdown/JSON artifacts are saved locally. Selected inputs go to the configured model for inference. Revisions link back to their earlier result. Orqanix shows them in its Results panel; another host may display tool output and local files differently. There is no automatic cloud session sync in the extension.
No. The market capability synthesizes exact selected sources, including their URLs and retrieval dates, and can propose questions or searches for missing evidence. Your host uses its own search tools and decides what to pass back. AxWise is not a replacement search engine.
The standalone extension speaks MCP over standard input/output for compatible hosts such as Goose and Codex. It uses the same core engine, with your own provider credentials. Host configuration, discovery, permissions and result rendering differ. Follow the repository’s setup examples for your host.
The project is being focused on its discovery and research capabilities as a local extension. The old dashboards and hosted orchestration are not part of this package. Video/pre-call tools and regional dashboards are not advertised as extension features. Existing repository history remains available; this is a new direction, not a promise of full legacy-web parity.
Keep your workflow. Add a specialist.