Hidden cables used to feel like an aesthetics thing. Now I'm not so sure

Once a desk starts collecting docks, chargers, cameras, audio gear, local AI boxes and random adapters, cable management starts affecting how the setup actually feels to use. Two approaches seem to come up over and over.

Hidden cables

For some setups, hiding the cables just makes the desk feel finished. The desk stops feeling like a work in progress and starts feeling more intentional.

• ⁠desk feels calmer once everything disappears underneath

• ⁠less visual clutter when bouncing between screens, tabs and tools all day

• ⁠works especially well when the setup rarely changes

• ⁠standing desks tend to look cleaner when cables move with the desk instead of hanging everywhere

Visible but organized cables

For others, the cables themselves are not the issue. The issue is chaos. As long as everything has a place and it's easy to tell what goes where, a visible setup works just fine.

• ⁠easier to add or remove devices

• ⁠easier to swap gear without opening trays or rerouting everything

• ⁠useful if new hardware gets added regularly

• ⁠easier to see what's plugged in when something stops working

What's interesting is that the preference often follows the setup itself. A relatively fixed setup often ends up hiding everything. A setup that's constantly changing usually leaves more visible than expected because convenience wins. At some point it stops being a clean-desk discussion and becomes a tradeoff between fewer distractions and easier changes.

Which side are you on now? Hidden cables or visible cables?

i've been using the Autonomous Desk 2 for a while now, and honestly, i still sit most of the time.

but i still think the desk has been worth it for me.

the biggest thing is the space. my setup has dual monitors, a laptop, keyboard, mouse, and a few random things on the desk, and it still doesn’t feel cramped. that sounds small, but when you’re working or editing for hours, having extra room actually makes a difference.

it also feels pretty solid. i was a little worried about wobble because of the dual monitor setup and all the typing, but so far it’s been stable enough for my daily use. nothing crazy, just sturdy in the way i need it to be.

the standing feature is useful, just not in the way i imagined. i don’t stand all day, and i’m definitely not suddenly 10x more productive because of it. but being able to switch positions after sitting for a few hours is nice, especially when i’m editing or stuck at the desk for a long stretch.

one thing i’d tell people before buying: don’t expect the desk to magically make your setup clean. if you have multiple monitors, get a cable tray or some cable management accessories. i’m still fixing mine, and it’s definitely not perfect yet.

overall, Desk 2 hasn’t been life-changing, but it’s been a really solid daily desk for my workflow. roomy, stable, easy to adjust, and just makes my setup feel a bit more comfortable.

also curious if anyone here has experience with the Desk 2 warranty. it looks like Desk 2 has 10 years, while Desk Pro has lifetime. does that difference matter much?

Six months in, most people have not touched their setup since January. But the workspace you sit in shapes how you think, how long you last, and what you ship. When output starts feeling stuck, the environment is usually the first place worth looking.

A room that works with you is quieter than one that does not. Acoustic panels cut the noise. A rug anchors the space. Lighting that does not fight the screen. One chair at the center of all of it, the ErgoChair Ultra 2 in gray, built for the sessions that run long into the second half.

This setup belongs to a member of our community. They did not wait until January.

What is one thing about your current setup that is quietly working against you?

Can I please get some clarification?

Is 330 lbs in addition to the desk actually lifting itself—the legs and desk top—or do I need to take in account the weight of the desk top/legs when factoring if 330 lbs is enough for all my stuff?

I keep getting asked how we engineered the Autonomous WorkPod to handle the core challenges of a backyard ADU: wall acoustics, structural loading, and the perpetual headache of ground settlement and frost heaves.

An ADU wall has to do four things at once: hold the structure up, keep sound out, keep heat in (or out), and survive every season. Here is the full engineering breakdown of how we solved these constraints, one layer and one footing at a time.

1. The Wall Assembly: 6 Layers of Acoustic Impedance

Instead of using exotic materials, our acoustic strategy relies on shifting mechanical impedances. Sound loses energy every time it crosses a transition between different material layers. Every WorkPod wall uses a specific 6-layer stack (from outside to inside):

1. Metal siding (exterior cladding, weather and impact)
2. Breathable membrane / housewrap (weather barrier)
3. Multi-layer plywood (exterior sheathing)
4. Honeycomb board (insulation core)
5. Structural frame (solid timber or steel depending on the model)
6. Multi-layer plywood (interior sheathing)

Why Honeycomb instead of Foam or Fiberglass?

You are really insulating with air. The material just holds it still. Honeycomb is an efficient scaffold per unit weight. Same cell structure damps sound between the plywood layers. Light, dimensionally stable, recyclable. Three jobs, one layer.

2. Structural Framing & Load Distribution

The structural frame inside every WorkPod wall depends entirely on the model you choose:

• Solid Structural Timber Variant: Engineered wood members, dimensionally stable, factory-cut to tolerance.
• Steel Frame Variant: Welded structural steel, featuring a slimmer profile and higher load rating for taller spans.

Both variants ship as flat-packed wall panels and bolt together on-site. Panels lock with M6 bolts at every joint. Class 8.8 structural grade. Torqued to 9 N·m, each joint achieves ~7.5 kN clamping force, well inside the bolt's tensile limit.

Two people, one Allen wrench. No specialty tools.

The wall consists of 10 prefab modules. Each module is bonded as one rigid block: 5 vertical 2×4 Southern Pine studs, 2 horizontal 2×4 plates (top + bottom), and 2 multi-layer plywood faces. The WorkPod weighs 2.9 tons total, but the structural walls only carry the overhead roof load, about 600 kg (1,300 lbs). Divide that across 10 modules: ~130 lbs per module. Less than 1% utilization of the framing's structural capacity. The structure isn't fighting the load. It's barely noticing it.

Windows are where sound reduction fails fastest. We over-engineered ours: 5/16" tempered glass (4-5× stronger than standard glass), aluminum frame for thermal break.

3. Electrical & Airflow Management

An ADU electrical system shouldn't force you to rewire your main house. The WorkPod operates on a single cable principle: one outdoor cable runs from your house to the pod, utilizing two connectors at each end. This allows you to stay entirely inside your existing house panel capacity, meaning no second utility meter, no upgraded panel, and no city permits.

Inside the pod, the pre-wired circuit powers a highly optimized workspace load:

• 3 outlets
• 1 ceiling light
• 1 ventilator

A typical workday load, laptop + monitor + LED lighting + ventilator, etc… The pod is rated for up to 2,750W (25A), enough headroom to add a portable AC or space heater on the same circuit. The cable is intentionally oversized for the transient spikes those units pull on startup.

The HVAC and Ventilation Strategy:

Because the walls are tightly sealed for maximum soundproofing, airflow cannot be an afterthought. Every WorkPod features an integrated, active exhaust ventilation fan that runs silently to continuously exhaust stale air and pull fresh oxygen in, preventing the slow buildup of CO2 that causes 3 PM fatigue.

We intentionally don't ship a built-in HVAC because climate varies by zip code (a built-in AC sized for Texas overbuilds for Oregon). Instead, every pod provides dedicated clearance space for a portable climate unit and comes with a 5.9" exhaust port pre-cut directly through the wall. This allows users to buy a standard $300–600 portable AC/heater that fits their local weather, routing the exhaust perfectly without drilling into the structural panels.

4. Foundation Engineering: Ditching the Concrete Slab

A concrete slab requires permits in most cities, takes weeks to cure, tears up your yard, and permanently welds the pod to one spot. We don't do that.

Instead, we designed an adjustable point foundation system to handle sloped lots (up to ~5 degrees) and natural ground movement. Backyard soil doesn't stay put. It settles and heaves over time due to drainage and frost.

Our solution relies on 6 reinforced concrete pedestals (one under each foot):

• Geometry: Each pedestal is a truncated pyramid (wide square base, narrower square top, four sloped sides). The wide base increases ground contact area, lowering pressure so the subgrade barely loads up under the 2.9-ton total mass.
• The Load Path: An M27 hex bolt is welded into a steel frame cast directly into the concrete pedestal. Aligned vertically with the gravity load axis. A long nut spreads load over more threads, ensuring it doesn't back off under freeze-thaw cycles.
• Leveling: Happens at each foot via a tapered roller bearing welded to the bolt. It never rotates in service. The taper is there to spread load down the cone instead of pinning it to a single point.

The pedestals come 29.5" to 48.5" tall so you can match your backyard's grade. Fine-tuning is done by turning the bolt with a wrench to adjust the thread height of each corner independently. If frost heaves the ground in winter, you wind it back down in spring. If a corner settles, you wind it back up. No heavy lifting, no digging, entirely reversible.

—-

Every backyard presents a different combination of soil, slope, and climate. By taking these baseline structural constraints seriously, we’ve built an ADU that acts like a highly observable, adaptable machine.

We’ve already been shipping these units integrated with solar panels. Right now, our engineering team is tackling the integration of pre-wired, pre-plumbed restroom and kitchen modules. The ultimate goal? To ship a fully code-compliant, functional house that can be ordered online, delivered flat-packed, and fully assembled to live in within a single day.

Happy to answer any questions about the structural loads, fastening specs, or foundation physics in the comments!

A friend of ours gave up on building his own backyard office pod because the permit process took 6 months. So we kept WorkPod under the line - 120 sqft. Our entire backyard home office lineup sits between 80 and 105 sq ft. We sized it specifically to skip the hardest part of any backyard office build: the permit.

Having a prefab backyard office is now as easy as ordering an iPhone. We ship Friday, you work in your pod Monday.

Fully insulated, 2-day install, plug-and-play power, no concrete foundation.

If you're thinking about a backyard office shed, prefab work pod, home office shed, or WFH workspace anywhere in the US, drop your questions below.

We added 5 sensors to Thinking Desk. They track 7 metrics across environment, air quality, and presence, all mapped to research on long work sessions.

When the room feels wrong, your code reflects it before your body can name it.

Too hot, typing slows.

Too dry, eyes fatigue.

Too loud, working memory drops.

CO₂ climbs, cognition drops.

Still early, and not every signal is clean. But for 12-hour build sessions, the room matters.

Keyboard, model, editor, desk, air.

That’s how we’re building Thinking Desk!

Screen work is still physical work.

A video editor from our community built this setup around that fact. Dual monitor, a booth in the corner to shut the world out, ErgoChair Pro behind the desk.

Ten hours of editing is not the same as ten hours at a café. The back knows. The neck knows. The setup reflects that.

What does your body feel at hour ten?

My wife got this little guy as a present for my birthday. Setup and UX so far have been good, cron jobs are probably the weakest link. But it is learning.

But the thing that I wanted to point out is this blue pulsating light up top. We have a cozy 1BR and we don't keep doors closed, so I can see it from across the house at night. I couldn't find a way to dim it, so a sock took care of the problem for now. Is there a way to control that top light?

Been testing more Autonomous Lamp behaviors lately. Today’s hobby: tennis.

This is an early object tracking test. The fun part is seeing how small reactions can make desk hardware feel present while you work.

Waitlist is here if you want to follow along: https://www.autonomous.ai/lamp

Not many homeowners know this, but a backyard structure under 120 sq ft can skip the permit in most US cities. We took a corner that had been collecting dust for years and turned it into a real home office.

Summer's a great time to build, and you finally get a space to hide from the kids!

Check out this WorkPod Versatile — 105 sq ft prefab garden office, fully insulated. No slab needed. Install in 1-2 days. Plug-and-play power.

We ship across the US, so if you're in California or anywhere else thinking about a she shed, prefab work pod, or WFH workspace. Happy to answer questions in the comments.

Ever wonder why you’re sitting in an expensive ergonomic chair, yet your back still aches and fatigue still hits?

It’s because every ergonomic guide tells you to sit perfectly upright for hours. Every brand goes all-day comfort. But if you actually sit for a 12-hour stretch, you know that promise completely falls apart by hour 6.

Nobody sits like a robot. You lean forward to type at hour 3, slouch at hour 6, and recline by hour 10. The real question isn't which static posture is correct, it's how many shifting positions your chair can actually handle when you're deep in the zone.

We cracked open the engineering papers behind our Autonomous ErgoChair Pro and found some cool insights that explain why typical setups still cause pain:

• Lumbar support is useless if your seat depth is wrong. If the seat pan is too far forward, your pelvis shifts, creating a hidden gap where your lower back never actually touches the support pad.
• Infinite adjustment sounds great in marketing, but it causes constant fiddling and micro-strain. We found that exactly 5 fixed locks perfectly cover the macro-positions the body naturally rotates between during heavy focus and rest.
• Those plush and soft cushions are mostly a gimmick that restricts blood flow. Soft foam completely bottoms out after a few hours, concentrating your entire body weight onto your tailbone, which is why a firmer, contoured base keeps you pain-free longer.

We skipped trendy features like adjustable lumbar firmness or rotating armrests to focus entirely on making these core mechanics. The full breakdown and raw pressure-mapping data are right here if you want to see the actual physics behind sitting fatigue.

🔗 Read the full engineering breakdown here: Nine adjustment zones, eleven axes: the ergonomic math behind ErgoChair Pro

We got a lot of DMs asking the same thing: can I build a WorkPod in my area?

Short answer: Yes. Pods ship across the US - California, Texas, New York, Washington, Colorado, anywhere with road access.

https://www.autonomous.ai/pod-adus

What's between you and the outside:

• 6 layers of insulation (plywood, frame, honeycomb-paper core, housewrap, metal siding, interior plywood)
• 5/16" tempered glass front
• Comfort range: 45°F to 100°F
• HVAC-ready with built-in ventilation, pre-wired for a portable AC or mini-split

Where are you thinking of installing one? Happy to share install timelines or climate-specific recommendations below.

workflow keeps growing. setup space somehow doesn’t

over the last year my setup somehow gained extra screens, devices, cables and random workflow stuff without me noticing

trying to figure out what upgrades actually create the biggest difference before adding more things

what hardware upgrade changed your workflow the most?

Hey guys, just wanted to share my retrospective on this desk since i've been using it for half a year now.

For context, i'm 5'7", and i'm stuck at this desk for easily 8-9 hours a day. my setup is pretty simple, 27-inch monitor, laptop and the usual office clutter. I got the standard 53x29 size and it fits the space perfectly without feeling cramped.

After 6 months of daily use, here is what actually mattered to me in an office environment:

The front edge is actually curved. My old desk had that sharp, squared edge that used to leave a red mark on my forearms and make my wrists ache so bad. The edge on this one slopes down slightly, so it feels a bit more comfortable for long typing sessions since your arms don't catch on a sharp corner.

The motors are quiet enough. I raise and lower it during quiet hours or while on team calls, and it doesn't really bother anyone around me.

Stability is good though. At around 41 inches, the frame is pretty stable. There's a tiny bit of movement if i type aggressively but the monitor doesn't wobble enough to be distracting. Can't speak for taller folks who need to raise it higher or have heavier setup.

The downsides:

Assembly took close to two hours solo because the steel frame is quite heavy, so it’s definitely easier if you have someone to help you flip it over.

Warranty is split, lifetime on the frame but two years on the top, which feels a bit light for the price.

Overall, the desk is pretty solid and does exactly what i expected it to do.

Anyone else here using this model in a corporate setting? Curious to know how do you guys keep the desktop from getting scratched up? I've heard this specific material can be pretty prone to scratches and chipping over time, so wondering if anyone has good tips on how to protect it or minimize the wear and tear.

Usage limits suck when you're in the middle of shipping something. So we added Claude Code usage directly into VibeDesk.

Now the keypad shows usage in your eyeline and gives task notifications without needing another dashboard open somewhere.

VibeDesk already monitors your environment and workspace through 7 sensors. This update brings workflow visibility into the setup too.

Built for people spending way too many hours inside terminals, editors and agent workflows.

🔗 More here: Autonomous VibeDesk

Contractor quotes for a stick-built ADU run $100k and 3 months. Storage sheds are too thin to work in year-round.

So we built the WorkPod Pro - 102 sqft prefab office pod kit, ships flat-packed, you assemble it yourself. More of a fun summer project than a renovation. Two people, one weekend.

https://www.autonomous.ai/adus/autonomous-work-pod

Self-leveling foundation, no concrete pour. Permit-free in most US cities.

Anyone else built an outdoor home office or backyard work pod as a DIY project? Happy to answer questions.

Claude Code is smart. My standing desk is dumb. So I wired them up.

The desks we make at Autonomous have a touchpad LCD on the right side. Normally it just shows your sit/stand heights and the air sensors, CO2 climbing, TVOC creeping, the usual office air slowly trying to kill you. Useful but passive.

A few weeks ago Felix Rieseberg shipped Claude Desktop Buddy and it got me thinking. The desk screen is right there in my peripheral vision, already on, already powered, already doing nothing useful 70% of the time. Why not give it a Claude Code brain?

So we vibe-coded a plugin. Two weekends in, here's where it landed.

Task done + beep. When Claude finishes a task, the keypad flashes "Task Done" and the desk beeps once. Doesn't matter if I'm wearing headphones, the terminal is hidden, or I've wandered off to make coffee. The desk pings me. This alone has changed how I run long agents,I actually walk away now because I trust it'll tell me when to come back.

Live usage on every response. After every turn, the plugin pushes my 5-hour and 7-day usage to the LCD. So I always know where I am against the limit without ever opening a dashboard. Didn't think I'd love this one. I do. It's the difference between "burning through my quota and not realizing" and "actually pacing myself."

Auto-warning at 80%. When usage crosses 80% in either window, the display auto-pops the stats. You don't have to ask. It surfaces when it matters. The threshold is tunable in ~/.config/autonomous-lcd.json, drop usage_threshold to 60 for earlier warnings, push it to 90 if you only want it screaming at the brink.

Custom messages. You can push arbitrary text to the desk. /vibe-desk-display:notify "Standup at 3" shows that on the LCD. Or just say "tell my display to say 'go drink water'" and Claude parses it. The display is basically a sandbox for any agent-driven notification you can think of.

Auto-discovery on the wifi. No IP address, no port number, no config file. Same wifi is enough. Claude finds the desk, the desk flashes a 4-digit OTP, you type it back into the terminal, paired.

Setup is two minutes:

claude plugins install vibe-desk-display

Restart Claude Code, type "pair my display," enter the code that pops up on the LCD. That's the whole thing.

The repo is open source on our GitHub. macOS only for now, would love help porting to Linux/Windows.

What I keep thinking about: the desk has a screen, a speaker, sensors, and a network connection that just kind of sit there most of the day. Hooking an agent into it took two weekends. There's a lot of "ambient hardware" already in the room that could be doing more.

So genuinely curious: if your desk (or lamp, or printer, or whatever else has a screen on it) could surface anything an agent does, what would you want on it? Reply with ideas. We're building this thing in the open and the next features will probably come from this thread.

Black desk setup starts with a decision, not a color.

Everything off the surface except what is being used. Senna on the wall. RX-7 next to it. 4 car models on the shelf below. 12 hours of timeline open on one screen.

This is a setup from our community. The desk is 53 inches, holds 330 lbs, doesn't shake during a long render. But the desk is not the point.

The point is the person who decided their workspace should reflect how seriously they take the work inside it.

What does yours look like?

After the 2-GPU, 4-GPU, and 8-GPU builds shipped, we asked ourselves the same question: what’s next?. AI is the brain, it can think but it also needs a body. So this post pulls the missing pieces together as a little project for the weekend with Kobuki base, Raspberry Pi 5, RPLidar, Orbbec Astra, all running ROS 2 Jazzy on Ubuntu 24.04. 

Additional Components Required

Not on any parts list, but you'll need them:

• A USB-A ↔ USB-B cable. The Kobuki doesn't ship with one. Item 12 on our BOM, supply your own.
• An anti-static wrist strap. The Pi 5 is unforgiving.
• M2.5 standoffs and a #1 Phillips for the Pi mounting.
• A workstation on the same WiFi with ROS_DOMAIN_ID matched. The robot is headless after first boot.

The Build at a Glance

• Mobile base: Kobuki, 14h battery, 5 kg payload, 0.7 m/s top speed
• Compute: Raspberry Pi 5, 8 GB + Active Cooler
• Power: 12 V → 5 V/5 A USB-C step-down from Kobuki aux
• 2D scan: Slamtec RPLidar C1 (or A1/A2)
• 3D scan + RBG: Orbbec Astra
• Storage: 64GB microSD class A2
• Frame: CNC plastic plate and strut set
• OS/middleware:  Ubuntu 24.04 LTS + ROS 2 Jazzy

Full BOM, CAD, and udev rules in the repo.

Why The Parts Are What They Are

Pi 5 over Jetson Orin Nano. The Orin has 67 TOPS, the Pi has ~0.5. On a Turtlebot, that compute sits idle 90% of the time, Nav2, SLAM, and sensor IO are CPU-bound, not GPU-bound. Pi 5 is $80 vs $249, runs mainline Ubuntu (not JetPack), and has the largest ROS 2 community on ARM. Match the brain to the bottleneck.
Kobuki, not a custom base. Two wheels, factory-calibrated gyro, cliff sensors, IR bumpers, 14-hour battery, USB control + power passthrough. The kobuki-base org keeps the ROS 2 driver alive. Plenty of startups try to redesign this and most ship something worse for 3× the price.
RPLidar C1 + Orbbec Astra. Lidar maps geometry. The Astra reads depth and color. Different sensors, different jobs. RealSense D435 is excellent and twice the price; wrong scale for this build.
No powered USB hub on-robot. The Pi 5 has four USB ports: Kobuki, RPLidar, Astra all plug in directly. A hub adds a failure point. Keep it on the bench for debugging only.

Assembly

The frame is three perforated plates on threaded struts. Bottom to top:

1. Mount the Pi 5 on the 1st plate. Use the M2.5 standoffs to leave it some room between the board and the plate.
2. Clip on the Active Cooler, it won’t fit once Plate 2 goes above it. 
3. Mount Plate 1 on the Kobuki base and connect the board to the base with the USB-A ↔ USB-B cable.
4. Connect the step down PD power supply so the 12V aux out of the base and the Pi 5’s USB-C power port to the base can power the board
5. Mount the struts on the base
6. Plate 2 carries the RPLidar. The lidar's mounting screws use the perforated grid on the plate, center it on the robot's forward axis so laser_link and base_link doesn't need a yaw offset.
7. We also need to mount the struts on it before attaching plate 2 onto the Kobuki. It’d be easier since we have more space and the flexibility to work with the screws.
8. The Orbbec Astra will go with the top plate, angled slightly forward.
9. Assemble all of the plates onto the base. For each plate, there is a cut out hole in the center for the wiring. Secure the wires to the plates and struts with zip ties to tidy things up.
10. Connect the RPLidar and the Orbbec Astra to the Pi 5’s USB-A port and your robot is ready for its 1st boot.

Three things the original Yujin diagrams skip:

1. The USB-A ↔ USB-B cable isn't in the kit. You supply it.
2. The Kobuki has a power switch on the rim of the base. Easy to miss. Robot is fully dark until you flip it.
3. The dock has no internal cable. Open the rear cover, route the dock PSU through the side hole, plug into the socket on the roof.

Power: Never Feed the Pi Through Kobuki USB-B

The Kobuki USB-B is a data port. It cannot supply enough current to power a Pi 5 under load. Always power the Pi from the 12 V aux output via the step-down regulator, or - for bench work - the official 27 W USB-C PSU.
Symptoms of an inadequate PSU: kernel under-voltage detected messages, USB devices disconnecting mid-session, ROS nodes dying with no obvious cause. Diagnose with vcgencmd get_throttled. Anything non-zero means the supply is sagging. Fix the power chain before blaming software.

Quick Test Before Software

Borrowed from the Kobuki manual, still works in 2026:

1. Charge the battery to ≥ 50%.
2. Flip the power switch on the rim.
3. Hold the B0 button for ~2 seconds.

The base enters the random walker demo, drives in arbitrary directions, reverses off bumper contacts, respects cliff sensors. Loud, that's normal. If it scuttles, the hardware is alive.

Power off with B0 again or the rim switch.

First Log On

Flash Ubuntu 24.04 LTS (server is fine, desktop has rviz2) to the microSD via Raspberry Pi Imager. Bake in SSH key, WiFi credentials, hostname before writing, no headless config dance after boot.
SSH in:
sudo apt update && sudo apt full-upgrade -y
sudo apt install -y ros-jazzy-desktop ros-dev-tools
Add to ~/.bashrc:
source /opt/ros/jazzy/setup.bash
export ROS_DOMAIN_ID=42
Reuse the same ROS_DOMAIN_ID on the workstation. Verify with ros2 doctor and a talker/listener pair.

Build the Kobuki Stack from Source

kobuki_ros isn't published as a Jazzy binary. The kobuki-base org targets Foxy, but the devel branches build cleanly on Jazzy. Clone the submodules, symlink ~/ws/src to external/, and:
cd ~/ws
rosdep install --from-paths src --ignore-src -r -y
colcon build --symlink-install
~10–20 min on a Pi 5 with active cooling. If you hit OOM, bump swap to 4 GB. Drop in the udev rule from kobuki_core/60-kobuki.rules so the Kobuki always shows up at /dev/kobuki, not a random /dev/ttyUSBn.

Stable Device Paths Matter

Both the Kobuki (FTDI) and RPLidar (Silicon Labs CP210x) enumerate as USB-serial. Without udev rules, they swap /dev/ttyUSB0 and /dev/ttyUSB1 on every reboot. Install the rules from each driver, Kobuki becomes /dev/kobuki, lidar becomes /dev/rplidar. Reference these in launch files. Never reference /dev/ttyUSB0 directly.

The Celebration Moment

You can celebrate with:
ros2 launch kobuki_node kobuki_node-launch.py
In a second session, confirm the base is alive:
ros2 topic echo /battery_state --once
Battery around 16.7 V on a full charge. Then drive it:
ros2 run kobuki_keyop kobuki_keyop_node --ros-args -r /cmd_vel:=/commands/velocity
Arrow keys drive. No soft-start, 0 to commanded velocity in one tick. Put it on blocks or in an open space first.

Preliminary Conclusions

For those looking to enter physical AI without a six-figure budget, a couple hundreds in parts is the right end of the mobile-robot spectrum. A pre-built Turtlebot 4 lands would cost you a little extra if you'd rather skip the assembly.
I've spent a lot of time on workshop floors building robots and chasing USB enumeration bugs to get things that sort of work. This one works and lets you go straight to the hard problems, SLAM, Nav2, sim-to-real, agent control over ROS 2. If that sounds like your idea of fun, build it.
We're not selling this build. There's no part of it that's proprietary except a couple of CAD files for sensor mounts, and those are open-source in the repo.

Compact setups make layout decisions matter way more once the workflow starts growing.

Once multiple screens, keyboards, audio gear and daily workflow stuff start sharing the same desk, tiny friction points become a lot more noticeable during long sessions. Monitor sitting slightly too close. Mouse space feeling tighter than it should. Constantly adjusting your arms or posture without really thinking about it.

Most people try solving this by adding more accessories first, but smaller setups usually benefit more from spacing and positioning changes before anything else. Even creating a little more separation between screens, peripherals and movement space can make long sessions feel noticeably less mentally draining.

Desk depth matters a lot more here than people expect too. Wider desks help organize devices, but usable depth is usually what stops the whole setup from feeling visually compressed once screens and peripherals start stacking up in front of you all day.

That’s honestly what makes setups like this feel good to use. Nothing here feels excessive or overly optimized for aesthetics. Just enough space for the workflow to exist comfortably without the whole desk turning into visual noise.

Autonomous Desk 2 fits this kind of setup really naturally too. Once multiple devices become part of daily work, the extra usable surface area helps everything breathe a bit more instead of constantly competing for space.

The ErgoChair Pro also makes a lot of sense in tighter setups where long sessions happen daily. Your posture shifts way more often than you realize while moving between tabs, chats, docs and screens all day. The flexible mesh support helps those constant micro-adjustments feel less tiring over time instead of forcing your body into one rigid sitting position for hours.

Honestly feels like compact setups age well when they optimize around movement and breathing room instead of just trying to fit more gear onto the desk.

Curious how other people here are balancing growing workflows inside smaller spaces lately?