issues Search Results · language:Dune language:TypeScript language:JavaScript language:JavaScript language:JavaScript
Filter by
34.9M results
Problem
AGENTS.md and README still read as otto connects to a local Letta runtime implying a separate install. Canon should
reflect embedded Letta inside otto while preserving:
Provider/API keys belong ...
documentation
enhancement
p1
size: s
seb-veto
Problem
#97 and #575 target zero-setup onboarding, but bootstrap is incomplete without: engine up → optional provider write-only
→ default agent → session.initialize().
This Mac should be the real default ...
enhancement
p0
size: l
Problem
Embedded mode should use ~/.otto/letta/ for Letta state by default, not dev ~/.letta/settings.json paths that leak into
user-facing errors (#605, #583).
Why it matters
One-app distribution needs ...
enhancement
p1
size: m
Problem
Bundling letta.js is necessary but not sufficient. otto must supervise its embedded Letta engine: start on launch,
health-check, recover from crash, clean shutdown, stable ports.
Today autodetect/connection ...
enhancement
p0
size: xl
Problem
This Mac (embedded) mode fails in packaged builds with:
Embedded mode: bundled letta.js not found under app resources or node_modules.
electron-builder.yml documents the target path, but @letta-ai/letta-code ...
enhancement
p0
size: l
Problem
Shipping letta.js inside otto.app requires confirmed redistribution rights for Letta OSS/components. This is a
one-way-door distribution decision — must be decided before bundle implementation ...
documentation
enhancement
p0
size: m
Problem
Product direction is settled: download otto → it works without a separate Letta Desktop install. Trust boundary is also
settled: credentials stay in embedded Letta, not otto config.
What is missing ...
documentation
enhancement
p0
size: s
Problem\n/build links users to /brokcode?project=..., but the BrokCode page does not read that project query param. The user can land in the wrong active/first project instead of the generated build.\n\n## ...
animvsh
Problem\nThe product can imply external one-click deployment, but the default project_id deploy path publishes through the managed in-app preview/app route unless Railway/webhook deployment is explicitly ...
Problem\nAnonymous /build sessions can show a preview-ready URL even when no BrokCode project was persisted, so users can click into an auth-blocked or project-not-found preview.\n\n## Evidence\n- app/api/build/stream/route.ts ...
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.