Here's where to get help with Chips.
Most answers are in the docs, and the guides below are the ones people need first. If yours isn't there, write to us.
Start with the guide for what you're doing.
Start here
A Chips server running, the app paired, and a harness saying hello, in ten minutes.
Read it →Install
The two lines from a release, what chips up asks, and every setting.
Read it →Connect a harness
One command for the harnesses Chips knows, and a link for the one you wrote.
Read it →The relay
How your phone reaches Chips away from home, and how to run your own relay.
Read it →Notifications
What reaches you, on which device, and when.
Read it →Tailscale
Chips on your tailnet, over https, for browsers on your other computers.
Read it →Here are answers to the questions that come up most.
My phone can't reach Chips away from home.
Away from home, your phone needs the relay. Set CHIPS_RELAY_URL and restart Chips. A phone you paired before learns about the relay the next time it connects, so you don't pair it again.
A browser on another computer won't pair.
A browser makes its key only on a secure address, which is localhost or an https address. Tailscale Serve gives Chips an https address that only your own devices can reach.
How do I update Chips?
Run the install line again. It puts the newest release beside the one you have and switches to it.
How do I stop Chips?
chips down stops the login service that chips up started.
Where should the Mac app be when I open it?
In Applications. A copy opened where it was downloaded runs from a folder macOS throws away.
You can write to a person about anything else.
Write to support@chipschat.ai.
For a bug or an idea, send us a feedback prompt: the change you want, written the way you'd ask a coding agent to make it.