AI tools I build, use or recommend for development, research and production, including my open-source projects like RepoSwarm, Graphlin, opstalk and embedrock.
Tools
Introducing Graphlin - a plugin for Claude Code/Codex that auto visualises your architecture as your agent is building it, and what the agent is currently working on. Why? I, like many others, tried Jev over the weekend. Unlike others, I did NOT build a router. I built a live diagram
Tools
So, I think Devops Agent is great. I went ahead and built a small CLI to talk to it directly from my terminal. I think it's pretty cool and makes it easy to jump in and investigate things fast. https://github.com/inceptionstack/opstalk Quick Install npm install
AWS
Happy to release bedrockify: An OpenAI Completions compatible API with embeddings proxy API for bedrock usage. Many of the current agents don't support bedrock by default, but do support custom OpenAI api. This gives a proxy you can run easily in one line on the same machine as
Tools
PSA: embedrock has been superseded by bedrockify which contains both the embedding and the completions inference proxy embedrock is a tiny Go proxy I created (ok, my agent did) that translates OpenAI's /v1/embeddings API to Amazon Bedrock, so your existing AI tools work with Titan and Cohere
ClaudeCode
What better time is there to try out a new tool or service than when joining a new company? Well, I just recently joined AWS as a Sr. Solutions Architect. Yay! And that's my opportunity to try out a bunch of stuff that I get a chance to
Cursor
A common thing for me and other developers I see do (I was first alerted to this by Harel Coman) . We work mainly with cursor but a few use claude code. But a common pattern is this: Start chat, then: 1. Enter Prompt 2. Choose model for this prompt 3.
Conferences
In a previous blog post I wrote about RepoSwarm: Give AI Agents Context Across All Your Repos . A few weeks ago I spoke at BuildStuff conference about this tool including a deep dive into its architecture and what you can do with it. Here's the link to the
MLOps
TLDR; see main image of this post, and this is the structure: AI Stack │ ├── Day-to-Day Chat │ ├── Development Centric │ ├── AI Coding Tools │ └── Background Coding Agents │ ├── Research Centric │ ├── AI Studio (Research) │ └── Model Training, Eval & Lifecycle │ ├── Production Facing │ ├── AI Gateways │ ├── AI Guardrails │ ├── Prompt Mgmt & Monitoring │ └── Agentic Frameworks │ └── Model Serving
Tools
TLDR; Go see it here. Intro Let's say you have 400+ repositories in your company. And you're: * A software architect that needs to understand what monitoring tools are used across all the repositories, and you want to ask an AI chat to help you * A Security
Introducing Graphlin - a plugin for Claude Code/Codex that auto visualises your architecture as your agent is building it, and what the agent is currently working on. Why? I, like many others, tried Jev over the weekend. Unlike others, I
So, I think Devops Agent is great. I went ahead and built a small CLI to talk to it directly from my terminal. I think it's pretty cool and makes it easy to jump in and investigate things
Happy to release bedrockify: An OpenAI Completions compatible API with embeddings proxy API for bedrock usage. Many of the current agents don't support bedrock by default, but do support custom OpenAI api. This gives a proxy you can
PSA: embedrock has been superseded by bedrockify which contains both the embedding and the completions inference proxy embedrock is a tiny Go proxy I created (ok, my agent did) that translates OpenAI's /v1/embeddings API to Amazon Bedrock,
What better time is there to try out a new tool or service than when joining a new company? Well, I just recently joined AWS as a Sr. Solutions Architect. Yay! And that's my opportunity to try out
A common thing for me and other developers I see do (I was first alerted to this by Harel Coman) . We work mainly with cursor but a few use claude code. But a common pattern is this: Start chat, then:
In a previous blog post I wrote about RepoSwarm: Give AI Agents Context Across All Your Repos . A few weeks ago I spoke at BuildStuff conference about this tool including a deep dive into its architecture and what you can
TLDR; see main image of this post, and this is the structure: AI Stack │ ├── Day-to-Day Chat │ ├── Development Centric │ ├── AI Coding Tools │ └── Background Coding Agents │ ├── Research Centric │ ├── AI Studio (Research) │ └── Model Training, Eval & Lifecycle │ ├── Production Facing │ ├── AI Gateways
TLDR; Go see it here. Intro Let's say you have 400+ repositories in your company. And you're: * A software architect that needs to understand what monitoring tools are used across all the repositories, and you want
