Electron + Python
A local desktop surface with a Flask backend and repository-aware tools.
Developer collaboration cockpit
Ask_IDA keeps the human in the loop.
A local development partner for exploring repositories, understanding code, asking for governed analysis, and carrying reviewed changes with traceability.
Boundary by design
Ask_IDA can analyze, clarify, refuse, request explicit consent, and help apply reviewed modifications. It does not own RegOS authority, learn automatically from every conversation, or turn a suggestion into a code change without review.
What it does
A governed workspace for development decisions.
Ask_IDA connects a developer to repository context and the IDA family runtime through a local Electron workspace. It helps make the next step legible before anything is changed.
Understand a repository Scan structure and dependencies, load a workspace from disk, browse files, and inspect the current repository state.
Ask for analysis Ask about architecture, code, repository state, or the next move, with clarification and refusal available when the request crosses a boundary.
Review before action Inspect proposed changes, use the terminal and planning surfaces, and keep code application attributable to a reviewed developer decision.
Learn only with consent Explicit approval is required before a development interaction becomes a learning request or durable memory artifact.
How it fits
A surface, not a shadow authority.
Ask_IDA is the developer-facing interface in the wider Hidden Canopy system. RegOS remains the authority layer, IDA remains interpretive, and reviewed code actions remain attributable to the developer.
IDA-TRAIN-V2
Reads the family runtime from the separate training workspace; it does not train models itself.
Reviewed changes
Suggestions remain suggestions until a developer reviews and accepts the resulting code action.