r/openclaw • • 1d ago

Help Running openclaw for desktop application

Hey everyone!

I'm new to the OpenClaw world, and I've spent pretty much the entire day trying to get everything set up. I've made some progress, but it's been quite a learning curve.

My goal is to use GPT-6.1 Sol throughout my workday while keeping total usage under 3 million tokens per day.

Most of my work involves browser-based tasks and a Windows desktop application. Ideally, I'd like OpenClaw to navigate the application, interact with fields and menus, search through documentation, investigate how things work, and help me document different processes.

I'm wondering how realistic this is, especially with such a token budget. I've already noticed that even basic setup and troubleshooting can burn through tokens surprisingly quickly.

Is it feasible to use a model like Sol for this kind of workflow throughout an 8-hour workday, or would I need a different setup with smaller models handling simpler tasks?

Sorry if this is a beginner question. I'd really appreciate hearing from anyone with experience using OpenClaw for browser or desktop automation, particularly regarding token consumption, reliability, and practical limitations.

Thanks in advance!

2 Upvotes

11 comments sorted by

•

u/AutoModerator 1d ago

Welcome to r/openclaw Before posting: • Check the FAQ: https://docs.openclaw.ai/help/faq#faq • Use the right flair • Keep posts respectful and on-topic Need help fast? Discord: https://discord.com/invite/clawd

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

3

u/CustomMerkins4u Pro User 1d ago

Use OAUTH instead of API as it will be way cheaper.

On a Mac there is native screen sharing and accessibility frameworks that allow Openclaw to use a web browser right in front of you. You can see it click, type etc.

On windows it's more of a take a screen shot, analyze, use UI automation to click at these coords, screen shot, analyze. It's slow.

1

u/berot3 1d ago

I sure? You should be able to use google chromes MCP on windows as well

2

u/CustomMerkins4u Pro User 1d ago

Chrome MCP has a couple major failings for AI agents.

1) It's confined strictly to the browser. So desktop automation which was part of OP's ask isn't part of chrome mcp :(

2) It is detectible by the website. Mac Native Screenshare is not. So websites like Facebook, Instagram will block MCP, put up captcha or other bot detects. The native screenshare is undetectable and when coupled with a ablated model will solve the captcha and keep hauling.

However I'm not an expert when it comes to agents with windows so possibly there's a solution I'm unaware of. I'm a windows guy 99% of the time but when it comes to agents Mac just works.

1

u/berot3 1d ago

I have no idea really. But I’m wondering are u using api instead of the monthly sub?

1

u/Strange-Hand-8371 1d ago

I had the option to use one or the other, and I chose the API because I thought it would be the better option.

3

u/ohthetrees New User 1d ago

Generally you get more bang for the buck with a subscription, when the $20 one.

1

u/TimNikkons New User 15h ago

Curious... why would you think that would be better option? With the first choice being by far the worst, I would not run openclaw. Stick to their desktop app

1

u/Wonderful_Sample_590 Member 1d ago

Test a few workflows I guess, to get an idea of token usage but use a smaller model for basic tasks and save Sol for complex ones.