Coding tools
Tools and workflows I use with Codex and Claude.
ship_or_revise = reviewed
These notes describe the implementation without client-specific details.
Problem
Keeping track of agent sessions and reviewing their changes.
I use coding agents for exploration, editing, and checks. These tools help me keep project context, follow sessions, and review the changes. Ocelin brings session previews and searchable history together locally, with an optional Windows app.
How it works
Define the task
I set the scope and review design decisions as the work develops.
Reuse common operations
Hooks, commands, and MCP servers support tasks I repeat across projects.
Keep project context
Repository mapping helps locate related code before making changes.
Check the changes
Tests, verification steps, and review are part of the development workflow.
Tradeoffs
Automation & checking
Agents can help with routine work, but their output still takes time to check.
Autonomy & review
Review steps keep consequential changes subject to a person’s approval.
Convenience & maintenance
Reusable commands make repeated tasks easier, with some setup and maintenance cost.
Checks
- Scoped tooling
- Keep operations within the task’s intended scope
- Test + verify loops
- Check changes against expected behaviour
- Human review
- Review changes before merging
- Named workflows
- Make repeated operations easier to follow
My contribution
I develop and maintain tools for my coding workflow.
- agent workflows
- MCP tooling
- quality gates
- review discipline
- final merge call
This includes Ocelin and the commands, hooks, and review steps I use around coding agents.
Tools I use to follow agent sessions, find previous work, and organise coding tasks with tests and review.
- MCP / hooks
- agentic commands
- quality gates
- cross-repo mapping
- review passes
- test + verify loops