Apparently with improved memory (no compression) and what it calls “dream and distil”: background organising of its understanding of a project’s code base and the user’s workflow habits, and writing skills for itself to support your workflow.
It’ll be interesting to see how that latter option turns out.
Dump the source code into a folder on your machine,
cdto it, then open mimo/opencode (it opens in the folder you are currently in terminal). In plan mode (tab to switch to it) tell it exactly what you want, e.g. “this is a dead android app, I want to add the following features to it: 1. 2. 3.” (use ctrl+J to line break, I don’t think it changes anything for the LLM but it’s easier on our eyes lol). Initial prompts are usually very long, you can really fill it in.If you only have the apk you can tell it that as well, “what do I need to do to add these features” and it will figure out your options. It’s scarily fast at first but you get used to it. It will guide you through a plan that you can refine, brainstorm, etc and when you’re ready, switch to compose with tab and say something like “ready to implement what we planned” (or “okay, let’s do it” if you want to sound cool).
Careful: mimocode and opencode has no permission gates out of the box, meaning it will start running commands and tools without asking you. You only get asked for permission if it tries to do something outside of the working directory. On opencode I have a json file that gates some commands (anything that isn’t purely read-only needs to ask me for confirmation), but I haven’t found where to put it yet on mimo.
json code
{ "$schema": "https://opencode.ai/config.json", "permission": { "*": "ask", "read": "allow", "glob": "allow", "grep": "allow", "list": "allow", "lsp": "allow", "repo_overview": "allow", "skill": "allow", "external_directory": "allow", "todowrite": "allow", "bash": { "*": "ask", "tutor init":"deny", "tutor *": "allow", "ls *": "allow", "cat *": "allow", "head *": "allow", "tail *": "allow", "wc *": "allow", "nl *": "allow", "rg *": "allow", "grep *": "allow", "file *": "allow", "stat *": "allow", "realpath *": "allow", "readlink *": "allow", "dirname *": "allow", "basename *": "allow", "du *": "allow", "df *": "allow", "uname *": "allow", "echo *": "allow", "whoami": "allow", "id": "allow", "printenv *": "allow", "which *": "allow", "pwd": "allow", "type *": "allow", "uptime": "allow", "free": "allow", "ps *": "allow", "lscpu": "allow", "lsblk *": "allow", "git status": "allow", "git diff *": "allow", "git log *": "allow", "git show *": "allow", "git ls-files *": "allow", "git describe *": "allow", "git rev-parse *": "allow", "git stash list": "allow", "git blame *": "allow", "qalc *": "allow", "tmux has-session *": "allow", "tmux capture-pane *": "allow", "tmux list-sessions": "allow", "tmux list-panes *": "allow", "tmux display *": "allow" } } }Isn’t there a mode or something like that where it never tried to modify any file or run any command? I would rather it just help me figure out what to do.
Yeah that’s plan mode. You can also literally tell it that’s what you want. Something like:
Add this to your long term memory: I don't want you to actually modify any code, just guide me. You can write tutorials and guidance documents. Don't edit code.