Skip to content

Commit db43a86

Browse files
committed
File tasks for open TODOs and update submod
1 parent d90641b commit db43a86

File tree

17 files changed

+388
-1
lines changed

17 files changed

+388
-1
lines changed

.beads/issues/hp-10.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: Path setting for sessions is busted
3+
status: open
4+
priority: 2
5+
issue_type: task
6+
created_at: 2025-12-01T19:35:06.196790047+00:00
7+
updated_at: 2025-12-01T19:35:06.196790047+00:00
8+
---
9+
10+
# Description
11+
12+
When I go New Session, then click the path button, then enter path, then click Checkmark, it goes back to the previous screen with the PATH UNCHANGED. Repro this bug in an e2e test then fix.

.beads/issues/hp-11.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: Sending messages to dead sessions has silent failure
3+
status: open
4+
priority: 2
5+
issue_type: task
6+
created_at: 2025-12-01T19:35:07.933099263+00:00
7+
updated_at: 2025-12-01T19:35:07.933099263+00:00
8+
---
9+
10+
# Description
11+
12+
If I have a totally dead session (nonexistent, probably never got a successful message from the connected machine), why can I still send multiple messages to it with no error? Whether message sending is sync or async, we should display a warning or error.

.beads/issues/hp-12.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: Update Last Seen on all web surfaces
3+
status: open
4+
priority: 2
5+
issue_type: task
6+
created_at: 2025-12-01T19:35:09.106425363+00:00
7+
updated_at: 2025-12-01T19:35:09.106425363+00:00
8+
---
9+
10+
# Description
11+
12+
Example: Machine page. Is this even in the local time zone? In addition to '11/30/2025, 11:42:49 AM' it would be great to print how long ago that was: '11/30/2025, 11:42:49 AM; 10 min, 38 seconds ago.' Use the same printing logic already in the codebase for human readable time deltas. Don't duplicate code\!

.beads/issues/hp-13.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: Audit mentions of 'handy' in codebase
3+
status: open
4+
priority: 2
5+
issue_type: task
6+
created_at: 2025-12-01T19:35:10.734234611+00:00
7+
updated_at: 2025-12-01T19:35:10.734234611+00:00
8+
---
9+
10+
# Description
11+
12+
The project was called 'handy' before 'happy'. Grep (case insensitive) all mentions of 'handy' in the repos and summarize how many and what they are. Consider whether we can rename them all to 'happy' but plan it out first - don't implement yet.

.beads/issues/hp-14.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: Build iOS app without Xcode
3+
status: open
4+
priority: 2
5+
issue_type: task
6+
created_at: 2025-12-01T19:35:11.873948640+00:00
7+
updated_at: 2025-12-01T19:35:11.873948640+00:00
8+
---
9+
10+
# Description
11+
12+
Investigate building the iOS app without using Xcode directly. There may be a way to do this.

.beads/issues/hp-15.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: \!commands don't pass through properly
3+
status: open
4+
priority: 2
5+
issue_type: task
6+
created_at: 2025-12-01T19:35:13.867048466+00:00
7+
updated_at: 2025-12-01T19:35:13.867048466+00:00
8+
---
9+
10+
# Description
11+
12+
When entering '\!pwd' or '\!ls' in Claude Code, this is passed through as a shell command without wasting model tokens. But via Happy it's passed to the AI agent which kind of works but has more waste. We should properly pass through '\!' commands.

.beads/issues/hp-16.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: Add stored shell commands for machines
3+
status: open
4+
priority: 2
5+
issue_type: task
6+
created_at: 2025-12-01T19:35:15.093659925+00:00
7+
updated_at: 2025-12-01T19:35:15.093659925+00:00
8+
---
9+
10+
# Description
11+
12+
Add a way to enter/save commands on the machine/<hash-id>/ page. New section 'Stored Shell Commands', similar to previously used paths. Each command has a 'Play' button. Pressing play launches the command in a subprocess of the happy daemon on that machine (show PID). Runs async, allows navigating away. REQUIRES INTERACTIVE PLANNING - don't implement until plan is approved.

.beads/issues/hp-17.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: Add HTTPS support
3+
status: open
4+
priority: 2
5+
issue_type: task
6+
created_at: 2025-12-01T19:35:17.117707507+00:00
7+
updated_at: 2025-12-01T19:35:17.117707507+00:00
8+
---
9+
10+
# Description
11+
12+
Create feature branch 'ssl' (following Makefile branching protocol). Enable secure access at https://ffh.duckdns.org:8081. Use the easiest approach / path of least resistance. REQUIRES INTERACTIVE PLANNING - don't implement until plan is approved.

.beads/issues/hp-2.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
title: Eliminate null-returning functions - adopt fail-fast error handling
3+
status: open
4+
priority: 2
5+
issue_type: task
6+
labels:
7+
- code-quality
8+
- error-handling
9+
created_at: 2025-11-30T15:53:31.531652716+00:00
10+
updated_at: 2025-11-30T15:53:31.531652716+00:00
11+
---
12+
13+
# Description
14+
15+
The codebase has many functions that return null on failure instead of throwing errors. This leads to silent failures that are hard to debug.
16+
17+
## Problem
18+
'Just returns null' is an anti-pattern. Functions either succeed or should generate clear errors.
19+
20+
## Scope
21+
Identify and document all places where we have 'return null' behavior, especially:
22+
- Encryption/decryption functions in webapp
23+
- API response handlers
24+
- State management functions
25+
26+
## Goal
27+
Make the project null-safe with explicit error handling everywhere.
28+
29+
## Investigation Needed
30+
- Determine if TypeScript strict null checks can help identify these patterns
31+
- Create an audit of current null-returning functions
32+
- Prioritize which functions to fix first based on impact

.beads/issues/hp-3.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
title: Add error banner system to webapp for user-visible errors
3+
status: open
4+
priority: 2
5+
issue_type: task
6+
labels:
7+
- ux
8+
- error-handling
9+
- webapp
10+
created_at: 2025-11-30T15:53:42.692022814+00:00
11+
updated_at: 2025-11-30T15:53:42.692022814+00:00
12+
---
13+
14+
# Description
15+
16+
We've had many silent failure conditions where the user has no idea something went wrong. We need a system to surface errors visibly in the UI.
17+
18+
## Problem
19+
- Machine fetch failures are silent
20+
- Auth validation failures don't show in UI
21+
- Decryption failures are only logged to console
22+
- Socket disconnections may not be obvious
23+
24+
## Requirements
25+
- Global error banner component that can be triggered from anywhere
26+
- Should support different severity levels (error, warning, info)
27+
- Auto-dismiss for non-critical errors
28+
- Manual dismiss for critical errors
29+
- Works on both web and mobile
30+
31+
## Investigation
32+
First check if such a system already exists (toast notifications, Modal system, etc) and extend it if so.
33+
34+
## Initial Use Case
35+
Show banner when machines API fails to fetch or returns empty unexpectedly.

0 commit comments

Comments
 (0)