Skip to content

add org level context and space level profile#1002

Merged
MaheshtheDev merged 2 commits into
mainfrom
feat/org
May 26, 2026
Merged

add org level context and space level profile#1002
MaheshtheDev merged 2 commits into
mainfrom
feat/org

Conversation

@ved015
Copy link
Copy Markdown
Member

@ved015 ved015 commented May 25, 2026

More Section

Screenshot 2026-05-26 at 3 12 24 PM

Dropdown opens on clicking more

Screenshot 2026-05-26 at 3 12 35 PM

Space profile section

Screenshot 2026-05-26 at 3 12 49 PM

Organisation Section with same button and colour style as existing

Screenshot 2026-05-26 at 3 06 33 PM

Modal opens with same colour scheme as rest

Screenshot 2026-05-26 at 3 06 47 PM

Disable manage

Screenshot 2026-05-26 at 3 06 59 PM

Improvised the ux a little bit to add prompt

Screenshot 2026-05-26 at 3 07 12 PM

Final look after saving org context

Screenshot 2026-05-26 at 3 07 33 PM

@graphite-app graphite-app Bot requested a review from Dhravya May 25, 2026 16:31
@claude
Copy link
Copy Markdown

claude Bot commented May 25, 2026

Claude finished @ved015's task in 1m 15s —— View job


Reviewing PR Changes

  • Analyzing PR context
  • Reviewing code diff for bugs and security issues
  • Checking boundary code and surrounding context
  • Submitting review

Overview: Adds organization-level context settings and space-level profile panels to let users guide how Nova processes content and view what Nova "knows" about each space.

Issues found: None — this looks good to ship.

The code is well-structured:

  • Hooks properly guard queries with enabled checks for orgId and containerTag
  • Mobile/desktop responsive handling is clean with modal vs panel pattern
  • State management is straightforward with optimistic UI and proper loading states
  • The API schema change is handled defensively (supports both old and new response formats)
  • No security concerns — credentials flow through standard patterns

Score: 9/10

Minor observations (not blocking):

  • useUpdateOrgSettings uses raw fetch while useOrgSettings uses $fetch — this works fine but loses retry logic for mutations. Not a bug, just inconsistent.
  • Template prompts are hardcoded in the component — fine for now but could be extracted to a config if more templates are added.

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented May 25, 2026

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
supermemory-mcp 2f61a70 May 26 2026, 09:49 AM

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented May 25, 2026

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
supermemory-app 2f61a70 Commit Preview URL

Branch Preview URL
May 26 2026, 09:50 AM

Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview: Adds organization-level context settings and space-level profile panels to let users guide how Nova processes content and view what Nova "knows" about each space.

Issues found: None — this looks good to ship.

The code is well-structured:

  • Hooks properly guard queries with enabled checks for orgId and containerTag
  • Mobile/desktop responsive handling is clean with modal vs panel pattern
  • State management is straightforward with optimistic UI and proper loading states
  • The API schema change is handled defensively (supports both old and new response formats)
  • No security concerns — credentials flow through standard patterns

Score: 9/10

Minor observations (not blocking):

  • useUpdateOrgSettings uses raw fetch while useOrgSettings uses $fetch — this works fine but loses retry logic for mutations. Not a bug, just inconsistent.
  • Template prompts are hardcoded in the component — fine for now but could be extracted to a config if more templates are added.

@MaheshtheDev MaheshtheDev merged commit 9229c60 into main May 26, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants