Coding workflow
Odysseus coding guide
Odysseus can be useful for coding once the model and tool access are configured carefully. Start with read-only project context, then add write access only after you trust the workflow.
1. Start with a coding-capable model
For coding, pick a model that can follow instructions and handle long context. Small models are fine for quick explanations, but code review and refactoring need stronger reasoning.
- Use Ollama for a simple local setup.
- Use vLLM if you need more throughput on a strong GPU.
- Use OpenRouter if you want hosted coding models without local inference.
2. Give Odysseus project context safely
Do not point an agent at your entire home directory. Create a narrow project folder, then expose only the files needed for the task.
git status --short
git diff --stat
git diffThese commands are often enough for an assistant to understand a change without broad filesystem access.
3. Add GitHub or filesystem MCP carefully
MCP can make coding workflows much stronger, but it also increases risk. Start read-only, test on a throwaway repository, and avoid production credentials.
Useful coding prompts
Review this diff for bugs, regressions, security issues, and missing tests. Prioritize concrete findings. Debugging
Here is the error and the relevant file. Explain the likely root cause and propose the smallest safe fix. Refactoring
Suggest a refactor only if it reduces complexity without changing behavior. Keep public APIs stable.
Coding safety rules
- Keep backups or commits before asking an agent to modify files.
- Review every diff manually.
- Run tests after generated changes.
- Do not expose API keys, private SSH keys, or production secrets to tools.