simonw / simonw/llm-coding-agent
Any interest in a home for the action log, beyond SQLite?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 37
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
I've been reading through llm-coding-agent — logging each action to SQLite as it edits files and runs commands is a neat, inspectable approach.
Curious whether you've thought about giving that log a browsable home outside raw SQLite rows — something like a board of what the agent did or is doing. I work on Elixion, an MCP-connected issue tracker built for roughly that use case. Not claiming it plugs into this specific project yet — genuinely just curious whether that's a direction you've considered, or whether SQLite is deliberately enough.
More here if useful: https://elixion.ai/. Also happy to just talk — 7@elixion.ai.
No pitch intended, just curious given how much you write about agent tooling.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue mentions the existing SQLite action log and a possible browsable home outside raw SQLite rows, but names no files, tests, or entry points. Start by reviewing how the action log is stored and displayed, then clarify the desired scope and what an acceptable browsable result would be.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- ai-infra-agents, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100