About

Building developer tools, from the language up.

I build Almide and tools for the people and agents writing code.

I design and develop Almide, a statically typed language. My work spans the implementation in Rust, the standard library, editor support and runtimes: the pieces that make a language usable.

I use that language in my own development: gramide for syntax trees, hew for reading code by structure, and porta for running agents in isolation. Building tools I use helps me refine both the language and its tools.

Hiromi Motodera
Hiromi Motodera
Language & developer tooling
Rust
Compiler implementation
Almide
Language & tools
AI
Agent infrastructure
Core projectAlmide — a statically typed language
ScopeFrom language design to everyday tools
Code toolinggramide / hew / codopsy
Executionporta / homullus
Design & buildSpecification, grammar, library, runtimes

Work

12 / 195

One from each family, the one most worked on. The rest are in the list.

See the whole list (195)

Selected work

O6lvl4「almide」

almide

A statically typed language built for one thing: code that survives AI edits

What it does

  • One metric: how much code still passes after an AI's edits
  • Diagnostics that name the one fix, not a list of guesses
  • Native via Rust and WebAssembly, byte-identical output
O6lvl4「hew」

hew

Read code the way a model should: cat, grep and sed for coding agents

What it does

  • Name a function or type, get exactly that back
  • Numbered, sized output: no line the agent did not ask for
  • grep folds repeats and names the function each match sits in
O6lvl4「porta」

porta

Run an agent with only the permissions you actually granted it

What it does

  • OS-enforced limits for the CLI agents you already use
  • A WASM runtime for the agents you build yourself
  • One porta.toml, and no Docker
O6lvl4「codopsy」

codopsy

Static analysis that scores 35 languages on one scale

What it does

  • 182 rules and complexity, summed up as a grade from A to F
  • Never runs your code: one binary, no compilers or language servers
  • Checks only the diff, and fails CI when quality drops
O6lvl4「golemide」

golemide

Read, edit, run the tests: a coding agent that solves more than Aider on the same model

What it does

  • 75.1% on Aider's 225-exercise polyglot benchmark for $0.45; Aider, same model and container: 67.1%
  • Given eight attempts, all 64 Rust and Python exercises, for $0.23
  • Every edit is syntax-checked before it is written
O6lvl4「comide」

comide

A coding agent in the terminal, in the line of Claude Code, Codex and Aider

What it does

  • Decides what to look at and what to change; golemide makes the edit and runs the tests
  • Its tools are programs that already exist: hew, gramide, golemide, ctxgate
  • Runs on Cloudflare, any OpenAI-compatible service, Anthropic, Gemini, a local server or your Claude login

What I have written

Repositories by language
Almide
TypeScript
Go
JavaScript
Rust
Python
HTML
Lean
Shell
CSS
C
Lua
Racket
Zig
Ruby
MoonBit
Dart
Makefile
Commits by org
almide32
O6lvl4123
almd-mc24

What I work on

From language to tools

I build both a language and the tools used with it. Around Almide, I develop syntax analysis, tools for reading and editing code, and agent runtimes.

Tools for reading code

In Almide, I build gramide for constructing syntax trees and hew for reading code by named functions and types. These tools help coding agents retrieve the code they need.

Infrastructure for AI

I also build what it takes to run AI for real: porta, which keeps an agent inside the permissions it was granted, and an agent runtime (homullus) and an LLM client (almai) written in Almide.

The figures — commits, first commit, languages — are measured from the clones. Commits are counted by author date, history shared between repositories is counted once, and a merge counts as one commit.