We're on X (Merge a PR, Get the Shoutout)
OFFYCE is on X now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor shoutout in open source.
OFFYCE is on X: x.com/offycecompany. Release news first, setup help fastest, floor screenshots welcome. And a workflow now watches the repo: merge a PR, and you're automatically granted the employee of the month role. We regret nothing about this feature and never will.
For a product that’s an office homage, we were weirdly hard to hang out with. Feedback lived in GitHub issues, launch threads on Reddit and Product Hunt, and an inbox we won’t discuss. Launch week made the gap obvious: between “formal bug report” and “shouting into a Reddit thread” there was nowhere to just… ask a quick question. Or post a screenshot of nine agents pulling an all-nighter.
So: x.com/offycecompany. The lobby is open.
What it’s for
Release news, first. We just shipped seven releases in eight days; X is where drops get announced the moment they’re tagged, and where we’ll be honest about what’s still rough.
Setup help, fast. A meaningful share of launch-week frustration was first-run problems that a two-minute conversation would have solved. If onboarding fights you, come fight back in a channel where someone’s awake — the community spans enough timezones now that someone usually is.
Show your floor. The screenshots people posted during launch week — offices mid-swarm, agents working through the night — were the best part of the whole launch. They deserve a wall. This is the wall.
Employee of the month
Here’s the part we’re irrationally proud of. Contributing to OFFYCE now comes with a
title: merge a pull request, and a GitHub workflow automatically grants you the employee of
the month role in the X. The PR template has an optional X: field so the bot
knows who to celebrate. No nomination committee, no monthly limit, no plaque in a hallway —
just a workflow that fires on merge, because in this office, recognition is automated too.
The inaugural class earned it properly: v0.4.4 carries nine community PRs — @gts-47 with eight, from atomic task-ledger writes to un-silencing an agent’s wake nudge, and @baziyer with the fix that stops the office floor rendering when nobody’s watching it. If you’ve been thinking about a first contribution, the good-first-issue path now ends with a job title.
The rules of the room
Short version: GitHub remains the source of truth — bugs and feature requests belong in issues, where they get triaged into real work rather than scrolling away. The X is for everything that’s conversation-shaped. Be kind, assume good faith, and if you built something weird with your hive, we absolutely want to see it.
The product has always been a bet that work is better with a floor full of colleagues you can see. It was overdue that the humans got a floor too. Come say hi: x.com/offycecompany.
FAQ
Where is the OFFYCE community?
x.com/offycecompany — also linked from the site nav, the footer, and the README. It's free, it's where release news lands first, and it's the fastest way to get help with a setup problem or show off what your floor is doing.
What is the employee of the month role?
Merge a pull request into OFFYCE and a GitHub workflow automatically grants you the 'employee of the month' role in the X. There's an optional X field in the PR template so the bot knows who to promote. It's a joke that's also completely sincere.
Why a X and not GitHub Discussions?
GitHub stays the home for issues and PRs — bugs belong where the code is. What launch week showed is that people also want a lower-stakes room: quick setup questions, sharing screenshots of their office floor, and hearing what's shipping before it ships. That's chat-shaped, not issue-shaped.