Typical workflow

The core usage of Mogick desktop is to combine sessions, files, terminals and result viewing around a local project. The following workflow can be used as a reference for daily use.

Understand an existing project

1. Create or select a project on the left.
2. Describe the scope you want to understand in the conversation area, such as "Explain the directory structure of this project."
3. When you need to focus on a file, right-click the file in the file tree on the right and select "Add to Chat".
4. Read the file cards, code blocks, and descriptions in the AI ​​output.
5. Continue to ask questions about unclear parts.

Check model files

1. Expand the model directory in the file tree on the right.
2. Click on the .mo file to view the text view.
3. Switch to graphical view to examine the model structure.
4. If an external modeling tool is required, right-click on the .mo file and select "Open in Sysplorer".
5. Write the inspection target into the session area and let AI help you summarize the model structure or locate anomalies.

Run the script and analyze the results

1. After activating the project, open the integrated terminal.
2. Execute your script or command in the terminal.
3. Use the terminal to find and locate key outputs.
4. Copy the relevant output to the conversation area, or add the generated result file to the chat.
5. Preview the result file in the product workspace on the right and open it with the default program if necessary.

Check the information and continue the conversation

1. Click the Browser button at the top of the workspace on the right.
2. Open the profile, document or local service page in the embedded browser.
3. Return to the conversation area to ask questions and continue analysis based on the current project.
4. If the address cannot be opened, check whether it contains http://, https:// or other valid protocols.

Review AI suggestions

1. First read the text description of AI and the list of files involved.
2. For suggestions on file changes, check the changes first and then decide whether to keep them.
3. For terminal command suggestions, first confirm the command function and path.
4. For uncertain operations, require AI to give smaller steps or read-only solutions.