ChatGPT Agent for cutting tips and SVG creation

I’ve put together an agent in ChatGPT to help with Maslow tuning, KrabzCAM settings, and SVG creation. It’s far from perfect so far but I intend to keep tuning it to make sure it’s reliable for settings suggestions. The hope is that it can give quality recommendations on bit types, feed and cutting speeds, and any other settings for any material you ask it.

https://chatgpt.com/g/g-6840cbbad8388191a0214fc624229d8d-maslowgpt

Right now my focus is on getting it to respond with the appropriate field names for KrabzCAM rather than other standard naming convention. I’m also hoping to find a way to connect it to the wiki here so it has more context specific to Maslow 4 and 4.1.

Any suggestions or feedback would be greatly appreciated!

8 Likes

This is super cool! I would love to integrate something like this into the forums to help get folks who are stuck somewhere a quicker response

1 Like

I’ll DM you and we can see what we can make.

1 Like

Alright so I am still working on this idea. I created a new agent and tied it into the forum here.

https://chatgpt.com/g/g-6840cbbad8388191a0214fc624229d8d-maslowgpt

hopefully it’s helpful to someone.

1 Like

This is really interesting. I tested it with some issues I’ve searched the forum for and it usually found what I was looking for. Some feed back is that it appears to contain a good bit of information from MakerMade and about the MakerMade CNCs. Perhaps that’s the intent, but if not maybe it could be filtered a little?

1 Like

OK I updated the agent to hard exclude MakerMade CNC and their forums. Let me know if you see this happening still.

2 Likes

I think that the distinction might be between the original chain driven Maslow design and the new belt driven design. There are a lot of things in common between the two designs, but also a lot of differences too.

I wonder if we even just want to have it reference the last six months or year of the forums so it’s pulling up to date information? Is there a way to make it prioritize that information but still know about the past?

Ah good idea! Let me add a condition for that. Should be able to handle it.

Edit: added a condition to only reference posts in the forum from the last 12 months. We’ll see how it works.

1 Like

This seems like an improvement, but I’m still seeing answers pulled from the older version:

I’d check if it’s referencing posts from the last 12 months, or posts that have comments from the last 12 months.

1 Like

That was a great catch. I added the following rules to the agent:
When searching the forum:
Only show results from threads or posts created since January 1, 2025.
If no relevant threads are found in that timeframe, clearly tell the user.
You may include older posts only as secondary context (label them accordingly).

So far it looks to be responding appropriately. Give it another try and let me know!

2 Likes

My test prompt has been “My sled is tilting while cutting, what can I do about that?” because we’ve seen a couple folks have that issue in the forums recently and it still seems to be giving me answers for the old version :confused:

Being pedantic, that could be interpreted as:

(threads or posts) created since January 1, 2025

Or

(threads) or (posts created since January 1, 2025)

Which is the problem with natural language.

What happens if you just use:

Only show results from posts created since January 1, 2025

Given threads are posts too?